Keep Codex Moving From Your iPhone

Your development machine does the work. Your phone handles the decisions that keep it moving.

5 min read

Codex on an iPhone is useful when the next step is a decision: clarify a task, approve a command, inspect a diff, or check whether CI finished. The code and build tools stay on a development machine. A phone is a way to keep that work moving when you leave your desk.

An engineer approves a code change from a phone on a park bench while a connected ghost agent works at a desk.

There are two relevant paths: OpenAI's own mobile remote connection and Agentastic Companion. This guide describes both, then walks through a Codex workflow in Companion. Agentastic publishes this guide about its own product; documentation and implementation were checked on November 13, 2026.

The official OpenAI option#

OpenAI's documentation describes connecting the ChatGPT mobile app to a desktop host. Start in the desktop app under Settings → Connections → Control this Mac or PC, select Set up or Add, and follow the QR pairing flow. Use the same account and workspace on both devices.

On iOS, open Codex, or Remote if your app still uses that label. Availability can vary by rollout and workspace policy. The host must be awake, online, and running the desktop app. Follow OpenAI's remote connection guide for current prerequisites and troubleshooting.

Choose this route when the sessions you want to reach already live in OpenAI's desktop workflow. The setup above is not the pairing flow for Agentastic Companion.

When Agentastic Companion fits#

Companion is useful when you run Codex inside Agentastic and want the same phone interface for its tasks, Claude Code tasks, repositories, worktrees, and review queue. You pair a Mac, then select the relevant instance and task rather than treating every terminal as an unrelated remote computer.

What you want to doWhere to look in Companion
Find a task waiting for a decisionFleet's Needs You filter
Read the conversation and send a follow-upThe task's chat
Inspect a live CLI sessionThe task's terminal
Check file changesThe diff review surface
Check a pull request and its CI stateThe pull request view
Reach a second MacPair that instance separately, then select its tasks

Phone actions retain their host and worktree context. Before approving anything, check that context: two tasks may refer to the same repository but be modifying different branches.

Set up Codex access in Companion#

First, start a Codex task in Agentastic on your Mac and confirm it works locally. Your provider login, project access, and command permissions must already be usable there. Agentastic's free app does not make model-provider usage or rented compute free.

  1. Open Settings → Mobile App on the Mac and install the iPhone Companion through the linked TestFlight beta. It requires iOS 18 or later.
  2. Enable Direct for a reachable local network or Tailscale connection. Alternatively, sign the Mac into Agentastic and enable Through Agentastic Servers; wait for Connected.
  3. Choose Pair Phone…. On the iPhone, use Settings → Pair an Instance to scan that code.
  4. Open the instance, select your Codex task, and send a small follow-up that asks it to summarize its current status.
  5. Enable notifications if you want requests and completion events to reach you while Companion is in the background.

You can enable direct and relay access together; the phone prefers direct endpoints before falling back. For network setup, pairing expiry, and the actual encryption design, read our Tailscale and relay walkthrough. That transport works the same way for Codex and Claude Code.

Give the agent a task you can review remotely#

Start with a bounded change and a reviewable result. For example:

Investigate why the empty search state is missing. Reproduce it, make the smallest fix in this worktree, and run the relevant tests. Explain the changed behavior and any checks you could not run. Stop before merging.

This is easier to supervise from a phone than “improve the app.” You know what outcome to look for, what evidence to request, and where the agent must stop.

For parallel work, put independent changes in separate worktrees. Read running Codex agents in parallel for the desktop setup. A phone dashboard does not prevent two agents from editing the same checkout; workspace isolation still matters.

Answer approvals with the right scope#

A permission prompt should show an operation you can evaluate, not just a button you can tap. Inspect the requested command or access, its working directory, and the reason the agent needs it.

For supported Codex Chat requests, Companion preserves the distinction between:

  • Allow once: permit the pending operation without making a session-wide choice.
  • Allow for this session: authorize the applicable scope for the current session.
  • Deny: reject the pending request and let the agent respond or choose another approach.

Notification quick actions are narrower. Allow Once and Reply require unlocking the phone; Deny can be available from the lock screen. A notification cannot silently become a permanent permission grant. Open the full task when the decision requires more context or a broader permission scope.

If an old notification does nothing, inspect the live task before retrying. Another device may have answered it, or the agent may have cancelled the request. Companion binds responses to the pending request rather than blindly replaying an old approval.

Review the result before merging#

When Codex finishes, read the explanation and the diff. Check whether the changed files match the requested task and whether the tests exercise the reported failure. A green status is useful evidence, but it does not establish that the product behavior is correct.

For a small change, the phone's diff and pull request views may be enough to decide the next step. For a broad refactor, a security change, or a UI interaction you need to exercise, ask for a draft PR and return to the desktop review environment. You can keep progress moving by requesting a missing test or explanation from the phone without immediately merging.

A useful follow-up is:

Show the reproduction before the fix, the check that now passes, and anything still unverified. Keep the PR in draft until I review the behavior.

Companion can show PR and CI state, but the repository's permissions and merge rules still apply. Do not confuse an agent's completion message with an independently verified release.

Understand the availability and privacy boundaries#

Companion's relay transports encrypted traffic between your paired devices; it does not host the Codex process. The Mac must remain awake and Agentastic must be running. Closing a laptop lid normally ends phone access until the Mac wakes. A remote SSH process may continue elsewhere, but Companion still reaches it through the Mac.

The phone-to-Mac secure channel protects application content from the forwarding relay. It does not prevent Codex from sending model requests to your configured provider, nor does it hide all connection metadata. Your unlocked phone and Mac are endpoints that can display the content. The connection walkthrough explains these boundaries, including the current static host-key limitation.

Finally, distinguish a running task from saved history. A conversation can remain visible after its original process exits. When returning after a restart, verify the host, branch, current files, and process state before continuing. Our session persistence guide explains what can be resumed and what needs to be restarted.

Frequently asked questions#

Can I use Codex on my iPhone?#

Yes. OpenAI documents remote host access in the ChatGPT mobile app. Agentastic Companion is another option for controlling Codex tasks running through Agentastic on a Mac. In either remote workflow, the phone controls a separate development machine.

Does Agentastic Companion require a VPN for Codex?#

No. You can connect directly over a local network or private VPN such as Tailscale, or enable the optional Agentastic relay for internet access. The relay requires the Mac to be signed into Agentastic.

Can I approve a Codex command from my phone?#

Yes. Supported Codex Chat permission requests in Companion offer Allow once, Allow for this session, and Deny. Notification quick actions offer a narrower Allow Once or Deny choice; session permission belongs in the full request view.

Does a phone connection keep a Codex process running?#

No. Process lifetime depends on the development host and session. A sleeping Mac is unavailable to Companion, and saved conversation history is not a running process.