You may start a Codex task at your desk, then need to leave before it finishes. Remote lets you follow that task in the ChatGPT mobile app, send another instruction, answer an approval request, and inspect the result without returning to the computer.
The important distinction is that the phone is the controller, not the work machine. Codex runs the task on the computer you connected, using that computer’s project, files, tools, and permissions. The computer must remain awake and online.
What Codex Remote does
Remote supports four parts of the working loop:
- Start: choose a connected computer and project, then describe a new task.
- Guide: follow progress and send additional instructions when the direction needs to change.
- Approve: review requested commands or actions before Codex continues.
- Review: inspect the response, changed files, diff, and test results before deciding what happens next.
This is useful when progress is blocked on a decision rather than on extended typing. A phone is well suited to approving a narrow command, clarifying one requirement, or reviewing a small follow-up diff. It is less suitable for reading a large architectural change line by line.
When Remote is useful
Remote works well for tasks that can continue on a prepared computer while you move elsewhere:
- monitoring a production build or test suite;
- answering a question that blocks an article or website change;
- reviewing a small bug fix and sending focused feedback;
- checking progress on a longer objective;
- starting work on the computer that has the correct project and tools.
It is unnecessary when you are already at the computer and need detailed visual inspection. It is also a poor time to approve an unfamiliar or high-impact command that you cannot evaluate comfortably on a small screen.
Create the project on your computer first
Prepare the project before leaving your desk. In my current iPhone workflow, Remote can open a project that already exists on the connected computer, but it does not provide the full desktop flow for creating and configuring a new local project.
On the computer:
- Create or open the project folder in the ChatGPT desktop app.
- Confirm that Codex can see the correct files and applicable
AGENTS.mdinstructions. - Check Git status and resolve any uncertainty about unfinished work.
- Run a simple read-only task so you know the project and tools are available.
- Give the computer and project clear names that will be easy to recognize on the phone.
Think of this as preparing the worksite. The iPhone is useful for directing an established project, but the computer remains the better place to create the project, confirm its boundaries, and handle initial setup.
Set up Remote
- Open the ChatGPT desktop app on your Mac or Windows PC.
- Go to Settings → Connections → Control this Mac or PC.
- Select Set up or Add, approve remote access, and finish any requested verification.
- Scan the displayed QR code with your phone.
- Sign in on the phone with the same ChatGPT account and workspace, then approve the connection.
- Open Remote in the ChatGPT mobile app and choose the connected computer.
Only connect devices you own and trust. Availability can depend on product rollout and workspace settings, so the controls may not appear for every account yet.
Start a well-scoped task
Remote does not reduce the need for clear boundaries. Choose the correct computer and project, then give Codex a goal, scope, constraints, and finish line.
Goal: Update the draft article's introduction for clarity.
Scope:
- Work only in the Blog Desk project.
- Modify the assigned article page only.
Constraints:
- Preserve the existing design and URL.
- Do not publish, deploy, or change hosting.
- Check Git status before editing.
Finish line:
- Run the normal build.
- Report changed files and verification results.A narrow prompt makes mobile review easier because the expected change and the allowed files are already clear.
Guide without constantly interrupting
Follow progress, but send a correction only when new information changes the task. Repeated “Are you done?” messages add noise. If an instruction is useful but does not change the current step, queue it for Codex to handle next.
When a task is risky or unclear, begin by asking for a plan. Review the proposed boundaries before authorizing implementation. For longer work, define a concrete completion condition such as “the build passes and the new route appears under the correct topic.”
Approve the narrowest necessary action
Remote can surface approval requests for commands, file changes, network access, and connected tools. An approval may apply once, to the current chat, or more broadly depending on the request and host configuration.
Do not approve everything merely to keep the task moving. For an unfamiliar command, a sensitive repository, or an effect you do not understand, approve only once—or deny the request and ask Codex to explain the command or propose a safer approach.
Before I approve this action, explain:
1. What the command will do
2. Which files or external systems it can affect
3. Whether it is reversible
4. Why the task requires it
5. Whether a narrower alternative existsKeep a separate way to reach the full computer
Remote usually keeps routine approvals inside the mobile workflow, but in my experience an approval message sometimes appears only in the desktop app. Product behavior can vary by app version, host configuration, workspace policy, and rollout. If the phone is your only way to respond, the Codex task may remain paused until you return to the computer.
For that reason, I keep a separate remote-desktop tool available. I use Chrome Remote Desktop to view and control the actual PC from my iPhone when I need to handle a desktop-only approval or inspect something Remote does not show.
Codex Remote
= start, guide, approve, and review the Codex task
Chrome Remote Desktop
= reach the full PC desktop when the mobile Codex view is not enoughSet up Chrome Remote Desktop on the computer before you leave, then connect from the iPhone app or web interface with your PIN. Google states that Remote Desktop sessions are fully encrypted. A remote-desktop connection nevertheless exposes the computer’s full interface, so protect the Google account with strong authentication, use a strong PIN, connect only your own trusted devices, and disconnect when finished.
This is a fallback, not permission to bypass Codex safeguards. Read the approval on the PC, understand its scope, and choose the narrowest acceptable option. If the command is unfamiliar or consequential, deny it and ask Codex for an explanation or safer alternative.
Review before accepting the result
When Codex finishes, open the changed-file summary first. Use the full diff when you need exact edits and open the source file when the diff lacks context. Inline comments are useful for precise corrections because Codex can address them in the same chat.
A good mobile handoff should answer:
- Did Codex change only the intended files?
- Did the requested checks pass?
- Is any conclusion based on an assumption rather than verification?
- Does the next action require a separate approval?
For publishing, deployment, deletion, spending, or infrastructure changes, keep the same approval boundary you would use at your desk. Convenience should not broaden authority.
A practical AIPeterLab example
At the computer
Connect the trusted Blog Desk computer
↓
On the phone
Start one scoped article revision
↓
Review any requested action
↓
Inspect the changed files and build result
↓
Request corrections if needed
↓
Send the finished draft to Site Management
Publication remains a separate approval.Remote is most valuable when it shortens the distance between Codex needing a decision and you making that decision. The computer still performs the work; the phone keeps you informed and in control.
For current setup details and availability notes, see OpenAI’s Codex Remote documentation. OpenAI also provides a deeper Remote engineering workflow guide. For the separate desktop fallback, see Google’s Chrome Remote Desktop instructions for iPhone and iPad.