Use mobile review without losing control
Steer and approve from a connected host
After this, you'll be able to decide when mobile remote control is appropriate and what to inspect before approving a Codex action from your phone.
Before you start
Complete Review diffs before commit first.
The idea
Mobile review is for steering a running Codex host. It is not a shortcut around review. Remote connections let you start or continue threads, answer questions, approve actions, and inspect outputs from a connected host.
Here is the before and after: before, Codex is guessing from a loose request. After, you can decide when mobile remote control is appropriate and what to inspect before approving a Codex action from your phone.
Now try it use the exercise prompt on one real repo task. Keep the output small enough to check before you accept the change.
You are ready when the Codex action, boundary, and proof all match the task.
Try it (10 min)
Watch out for
- Approving from a notification without opening the thread.
- Approving commands you would reject on desktop.
- Losing track of which host or repo the mobile session is connected to.
- Accepting a change without seeing test, diff, or screenshot evidence.
Paste this into Claude
Decide whether to approve this mobile Codex request: Task: [task name] Current Codex status: [paste status] Action requesting approval: [paste action] Visible proof so far: [tests, diff, screenshot, terminal output] Risk area: [files, network, secrets, deploy, data, unknown] Return approve, reject, or ask for more proof. Include the exact follow-up you would send from mobile.
What a good response looks like
Ask for more proof. Follow-up: 'Before I approve npm install, explain which package is missing, why the task needs it, and what files will change. After install, show package diff and rerun the failing test.'
What good looks like
- The decision is based on visible action and risk
- Unknown risk triggers a request for more proof
- Approval is narrow
- The follow-up asks for evidence, not reassurance
When this breaks
- Breaks when mobile approval targets the wrong connected host.
- Breaks when a risky command is approved because the phone view made the change feel smaller than it is.
AI can help with this
Use Codex to help you you can decide when mobile remote control is appropriate and what to inspect before approving a Codex action from your phone. Start with the exercise prompt and your real input. Ask for one draft, then check it against this proof: The decision is based on visible action and risk. Accept only the version you can verify yourself.
You can now
You can explain what mobile remote control does
- You can inspect action, risk, and proof from mobile
- You can ask for better evidence
- You can reject unknown-risk actions
Key takeaways
Mobile Codex keeps work moving, but it still needs review discipline. Approve only what you can explain.
- Mobile can steer, approve, and review connected Codex work.
- Small screens increase context-loss risk.
- Ask for proof before approving risky actions.
- Know which host and repo you are controlling.
Go deeper