A
Server mode
Best when you want a reusable server with URL and QR code.
shell · claude
claude remote-control
Remote Control
Claude Code
Codex
Choose the runtime before opening remote access
Both paths share the same local-first shape: a signed-in remote device talks through a relay, while the real session keeps running on a connected host. What changes is the host process, the identity system, and whether model routing is added.
What talks to what local-first
Phone / tablet / browser
Only sends control events and receives session updates.
Remote relay
Only forwards prompts, approvals, and status. Files and workspace stay on the host.
Local session
Runs the real Claude/Codex session. Files, tools, credentials, and approvals stay on the host.
Claude Code path
Use the built-in Claude Code command. Remote Control needs a claude.ai subscription login; API-key or Console auth cannot create the remote session.
Codex path
Use the Codex app-server host process. ChatGPT identity handles the remote relay; CLIProxyAPI/CCS only changes where model calls are routed.
Claude Code requirements
Check these before debugging QR codes or missing sessions.
Paid plan
Pro / Max / Team / Enterprise
claude.ai login
Sign in with your claude.ai account. API keys or Console tokens cannot create a remote session.
Team / Enterprise admin
For Team or Enterprise, an admin must enable Remote Control in Claude Code settings first.
Open Claude Code settings Trusted workspace
Trust each project once before controlling that session remotely.
Enable remote access
choose 1Pick one entry point. They are alternatives, not steps to run together.
B
Start a named session
Open a new Claude Code session with remote enabled immediately.
shell · claude
claude --remote-control "My Project" C
Inside active Claude Code
Type this inside the running Claude Code screen.
claude · interactive
/remote-control
# or:
/rc D
Enable by default
Open Claude Code config, then enable remote control for future sessions.
claude · interactive
/config
# Set: remoteControl: trueWhat is the Codex app-server?
Codex app-server is the local interface rich clients attach to for auth, conversation state, approvals, and streamed agent events. Remote Control starts that host process, then the remote device controls it through ChatGPT identity.
Local app-server
The standalone binary launches the daemon. Local files, shell, tools, plugins, and credentials come from this host.
Remote identity
ChatGPT/OpenAI OAuth authorizes the remote device and workspace. It is separate from provider routing.
Model routing
-c model_provider changes where model calls go after the app-server is running. CLIProxyAPI/CCS lives here.
Start Codex Remote Control
Install the standalone Codex binary once, then pick a start path: default OAuth, or route through CLIProxyAPI/CCS when you need shared routing and account-pool controls.
1
Install standalone Codex
one-timeRun the ChatGPT installer once. Both cases below reuse the binary at ~/.codex/packages/standalone/current/codex.
shell · install
curl -fsSL https://chatgpt.com/codex/install.sh | sh 2
Sign in with ChatGPT identity
OAuthRemote Control needs a ChatGPT/OpenAI OAuth session first. CLIProxyAPI only changes model routing; it does not replace the ChatGPT identity used to authorize the phone and host.
shell · ChatGPT OAuth
~/.codex/packages/standalone/current/codex login Open ChatGPT on phone
Use the same ChatGPT account and workspace, then open the Codex tab. If the Codex tab is missing, update the ChatGPT app first.
Approve host access
When ChatGPT asks whether this phone can access Codex on your computer, tap the authorize button. That is the device handoff shown in the mobile prompt.
Wait for secure setup
After approval, ChatGPT may show a secure setup spinner. Wait until the Codex host/session appears before sending prompts remotely.
Keep the host awake and online. Files, tools, credentials, sandboxing, and approvals still come from the connected host; the phone only sends prompts and receives session updates.
3
Start the daemon — pick a route
Run only one of the cases below.
A
Normal OAuth remote control
defaultPick this when you already signed in via ChatGPT/OpenAI OAuth and do not need CCS model routing.
shell · standalone
~/.codex/packages/standalone/current/codex remote-control start --json B
Remote Control + CLIProxyAPI/CCS
route modelPick this when CCS/CLIProxyAPI is healthy and you want account rotation, quota visibility, or failover behind the remote session.
shell · cliproxyapi
~/.codex/packages/standalone/current/codex remote-control start \
-c 'model_provider="cliproxy"' \
-c 'model="gpt-5.5"' \
--jsonTroubleshooting
Common errors when running remote-control start , plus a quick check that your binary exposes the right surface.
Preflight: check the Codex CLI surface
Before using either case, confirm your installed standalone binary exposes remote-control start / remote-control stop , --json output, and -c config overrides.
The standalone path should resolve to the Codex binary.
remote-control start manages the app-server daemon. -c overrides are parsed as TOML, so model_provider and model can be passed per start. "Connection is errored" on start
If remote-control start returns Remote control is enabled on <device> but the connection is errored , the cloud still tracks this device as enrolled but the previous app-server WebSocket ended in an error state (network blip, killed daemon, stale socket). Stop the local daemon first to clear state, then start again. If it persists, toggle the device off in ChatGPT → Remote Control settings before retrying.
shell · reset connection
~/.codex/packages/standalone/current/codex remote-control stop
~/.codex/packages/standalone/current/codex remote-control start --jsonApp-server socket is missing
If start fails with app server did not become ready on app-server-control.sock , the managed daemon did not create its control socket in time, or the old daemon state is stale. Check the daemon version/status, stop it, then rerun the same start command you chose above.
shell · socket reset
~/.codex/packages/standalone/current/codex app-server daemon version
~/.codex/packages/standalone/current/codex app-server daemon stop
# Then rerun the same remote-control start command you picked above.OAuth reset path
Last resort — use only when standalone Codex reports token_revoked or refresh_token_reused . Reset OAuth, then rerun remote-control start .
shell · reset oauth
~/.codex/packages/standalone/current/codex logout
~/.codex/packages/standalone/current/codex loginSources checked
The Claude and Codex sections above cover the main things to watch for. Use the official docs below when you want more detail.
Claude Remote Control docs Requirements, claude.ai login, Team/Enterprise admin toggle, local-session behavior, and limitations. Open official docs OpenAI Codex remote connections Connected host model, mobile setup, secure relay, and what comes from the host. Open official docs OpenAI Codex app-server Official definition of app-server as the local protocol/interface for rich Codex clients. Open official docs