Your phone as the control plane: a guide to mastering Codex Remote!

Hey everyone, it's Shiichan! Today I've got something exciting: driving your engineering work straight from your phone.

developers.openai.com

What was announced?

OpenAI's developer blog published a guide to mastering "Codex Remote". Codex Remote is a mobile app that turns your phone into an engineering control plane.

The key idea is that your code still runs where it belongs: on your own Mac, Windows machine, devbox, or other connected host. From your phone, you start, direct, review, and organize that work.

Why it matters

The most important thing is to NOT try to cram a whole terminal onto a tiny screen. The original puts it this way.

The code still runs where it belongs: on your Mac, Windows machine, devbox, or other connected host.

So the phone isn't a dev terminal, it's an interface for making decisions. That means even on the move, you can quickly handle the calls that matter: start, redirect, and review.

What changes

Before you send your first prompt, you can pick the host and workspace, the branch and worktree, and run environment setup. The guide says spending about 10 seconds getting the execution context right saves you a lot of cleanup later.

You can also attach photos, files, skills, and plugins on the very first turn, so you remove ambiguity about what you want done right from the start.

Dive Deep

Controlling execution

Queue: waits for the current response to finish before sending your next prompt (this is your default).
Steer: injects guidance mid-run to correct course (use it only when you need to change direction).

Side chats and goals

/side lets you ask a lightweight tangential question without disrupting the main thread. You can also select text and choose "Ask in side chat".
/goal creates a durable objective that spans many turns. For long work, the guide recommends goal-based objectives over repeatedly asking for status.
/plan toggles Plan mode, which proposes an implementation path before changing code.

Review

With /review, you get changed-file summaries and diffs, attach inline comments to specific lines, and compare branches. There's even line wrapping so long diff lines stay readable on a narrow screen.

Slash commands

/plan     Toggle Plan mode
/goal     Create a durable objective
/side     Lightweight side question
/review   Review changes or compare branches
/status   Inspect session and context usage
/compact  Compress a long thread
/fork     Start a new thread from history
/fast     Toggle execution speed

Permissions and thread hygiene

Commands, file changes, network access, and tool use surface as approval requests, and you can scope them to just this request or the whole chat. The trick is to pick the narrowest scope you need. /status shows your workspace, context usage, and rate limits, and you should archive finished threads aggressively to stay organized. There's also biometric protection with Face ID or your device passcode to keep Codex locked down.

Recommended mobile workflows

The original describes five patterns: the release captain (intervening only with Steer), interrupt-driven bug fixes (attaching screenshots and logs), the mobile reviewer, long-running objectives, and the multi-machine operator. Start by copying whichever pattern fits how you work.

Wrap-up

Codex Remote turns your phone into a control plane, while your code keeps running on your own machine.
Queue is the default, Steer is only for course corrections, and mixing /side, /goal, /plan, and /review is the key.
Approve permissions at the narrowest scope, and archive threads to stay tidy.
It's a perfect guide for engineers who don't want to stop reviewing or directing work just because they're on the move!