Codex IOS App control codex on Mac

Open 💬 5 comments Opened Apr 26, 2026 by frank-bluemke
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

iOS Codex App with Local Mac Session Continuity

What feature would you like to see?

Summary

I would like an iOS Codex app that can connect to a local Codex instance running on my Mac, allowing me to continue interacting with the same Codex projects, conversations, and active coding sessions from my phone.

The goal is to let users continue giving instructions, reviewing progress, approving actions, and managing Codex tasks when they need to step away from their computer.

⸻

Problem

Today, Codex is most useful when I am actively sitting at my Mac. If I need to leave my desk, I lose the ability to continue guiding the agent, reviewing its proposed changes, approving safe actions, or correcting direction.

This creates friction for workflows where Codex is doing iterative development work and needs occasional user input.

⸻

Proposed Solution

Create an iOS Codex app that can connect to the user’s local Codex environment on macOS and mirror the active Codex experience.

The iOS app should allow the user to:

  • View the same projects and conversations available on the Mac
  • Continue active Codex sessions from the phone
  • Send new instructions to Codex
  • Review proposed changes or action requests
  • Approve, reject, or modify requested actions
  • See progress/output from the local Codex instance
  • Resume the same conversation back on the Mac later

Connection Options

The app should support multiple connection modes:

Mode

Description

Local Network Connection

iPhone connects directly to the Mac while both are on the same Wi-Fi/network

Internet Relay / Remote Connection

Optional secure remote access when the user is away from the local network

Local-Only Mode

For users who do not want their local coding environment accessible over the internet

Ideally, the first version could start with local network support and expand later to secure remote access.

⸻

Sync Expectations

Projects and conversations should stay in sync between Mac and iOS.

The phone should show the same state as the Mac, including:

  • Active project
  • Current branch/session context
  • Conversation history
  • Pending approvals
  • Agent output
  • Tool/action requests
  • Current task status

The user should be able to move between Mac and iPhone without losing context.

⸻

Example Use Case

I start a Codex task on my Mac, such as implementing a feature or debugging an issue. Codex begins working, but then I need to step away from my desk.

From my iPhone, I should be able to open the Codex app, see the same active session, review what Codex has done, provide additional instructions, and approve safe actions.

When I return to my Mac, the same session should be updated with everything that happened from the phone.

⸻

Why This Matters

This would make Codex much more practical for real-world development workflows where the user does not remain at the computer continuously.

It would be especially helpful for:

  • Long-running coding tasks
  • Reviewing agent progress while away from the desk
  • Approving low-risk actions remotely
  • Giving additional instructions without interrupting the session
  • Maintaining momentum during breaks, errands, commuting, or meetings

⸻

Security Considerations

Because this would expose access to a local coding environment, the feature should include strong security controls, such as:

  • Explicit device pairing
  • User-controlled enable/disable toggle
  • Local-only mode
  • Optional internet access mode
  • Authentication for remote access
  • Clear indication when a phone is connected
  • Ability to revoke paired devices
  • Approval gates for sensitive actions

⸻

Suggested MVP

A reasonable first version could include:

  1. iOS app pairs with Codex running on macOS
  2. Local Wi-Fi connection only
  3. Read/write access to active Codex conversations
  4. Ability to send instructions
  5. Ability to approve or deny pending Codex actions
  6. Basic project/session sync

Remote internet access could come later as an advanced option.

⸻

Requested Outcome

Please consider adding an iOS Codex companion app that allows users to continue active Codex sessions from their phone while staying connected to their local Mac environment.

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #19657

Powered by Codex Action

jianmosier · 3 months ago

This is a use case I would also like to see supported officially.

A concrete reference implementation is here: https://github.com/jianmosier/codex-remote-iphone

It uses a small local bridge plus a phone web UI so an iPhone can pair with the desktop Codex session, send prompts, watch responses stream back, attach images, approve/deny command or file approval requests, and interrupt a running turn. The important part is that the phone does not directly expose Codex Desktop IPC or codex app-server to the internet; it goes through an authenticated bridge with local approval.

It would be very useful if Codex had a first-party mobile remote-control flow along these lines, especially for continuing or supervising a desktop session from a phone.

vansin · 3 months ago

Now that Codex mobile remote control is rolling out, could the team clarify the status of CLI support?

Specifically: is connecting ChatGPT mobile directly to a codex remote-control / Codex CLI session officially supported, or is mobile remote control currently intended to work only through the Codex desktop app?

If CLI support exists, it would be helpful to have a short documented setup flow and notes on whether it is considered stable or experimental.

hendryyeh · 3 months ago

Adding to @jianmosier's pointer — for folks specifically on @vansin's question about CLI (not Desktop) mobile control, a few community projects target that exact gap:

Architectures vary: some use Tailscale, some use a hosted relay, some are LAN-only. Worth picking the one whose security model + transport matches your setup. None are first-party, so trust scope is whatever the project itself defines.

Official Codex Mobile + Desktop Remote Control currently flows through the Codex Desktop app, not the CLI directly — confirmation on the CLI path would be helpful here.

Snailflyer · 3 months ago

Adding one narrower open-source option to the community-project list: https://github.com/Snailflyer/faryo

Faryo is not a native Codex Desktop / app-server mobile client. It takes the tmux route instead: Codex CLI / Claude Code / shell keep running as the live local session, and the phone/desktop browser workbench is only a control surface for output review, short input, approve/interrupt, and handoff.

That makes it a fit when the priority is “keep the same local CLI process alive and steer it from a phone” rather than mirroring the official Codex Desktop remote-control path. Current mature path is Linux + tmux + local CLI agent + browser/PWA.