How to use Codex from your phone

Start a Codex session on a machine you trust, then monitor, steer, approve, review, and continue from mobile — without turning your phone into a terminal.

Based on
CLI
0.2.17
Preview ref
a2c45c8

Codex works well, but the default ergonomics get awkward when a session runs longer than “one sitting”.

The moment you step away from your terminal, you usually lose the easy control loop:

  • check progress
  • send a clarifying instruction
  • approve a tool permission
  • review the changes

On a phone, you can brute-force it with SSH, but a phone makes a poor terminal.

So the problem is: keep the session moving (follow-ups, approvals, review) from your phone while Codex keeps running on the owning machine.

Happier is an open-source app that lets you run and orchestrate Codex, Claude Code and other agents cross-device, from your phone, desktop or the web. Trade-off: you still need auth + the right backend path set up on the owning machine for the flows you care about (attach/resume, etc.).

TL;DR

  1. Set up Happier and authenticate Codex on your machine (CLI or connected services).
  2. Start a Codex session from Happier (phone/web/desktop) and choose the machine that should run it.
  3. Since Happier 0.2.13 with Codex CLI 0.131.0+: the native Codex TUI and the Happier app connect to the same App Server thread. You can type in the terminal and approve from your phone on the same session, both live.
  4. From your phone: follow the transcript, send follow-ups, handle approvals, and review diffs.
  5. Switch to the terminal anytime with happier attach <session-id> — the session stays shared (macOS/Linux with App Server).

If you started a Codex thread directly with codex (not through Happier), Happier can't join it while it's running, because Codex keeps one active writer per thread.

The problem

Codex is good at doing work.

The friction is everything around it:

  • “Where is the session running?”
  • “How do I keep it moving while I’m not at my laptop?”
  • “How do I switch back to the terminal without forking the session?”

Authentication: get Codex logged in (without surprises)

Codex supports machine-local auth management in:

  • Settings → AI provider settings → Codex

From there you can:

  • see whether Codex is logged in on the selected machine
  • detect whether Happier picked up CLI login or OPENAI_API_KEY
  • open codex login directly inside Happier

You can also authenticate through Happier connected services:

  • subscription auth (device/paste flow)
  • or API key

CLI examples:

happier connect codex --device
happier connect codex --paste
happier connect codex --api-key

Backends: the part that trips people up with Codex

This is the Codex-specific nuance worth understanding.

Codex can run through multiple backends in Happier:

  • Codex App Server (default): the recommended path if you care about resumability and the app-first workflow.
  • Codex ACP: a fallback if you explicitly choose it.
  • Codex MCP: still fine for fresh sessions, but it’s not the normal vendor-resume path.

The two behaviors that matter in practice:

  1. For new sessions, Happier defaults to App Server and doesn’t silently fall back if it’s unavailable.
  2. For resume, Happier stays strict — it errors instead of quietly starting a fresh session.

Once those two rules are clear, Codex-from-phone stops feeling “random.”

If you’re new to Happier (what it is, and where to get it)

If you haven’t seen Happier before: it’s an open-source companion app (mobile/web/desktop) for AI coding agents like Claude Code, Codex, and OpenCode.

The workflow here is: use Happier from your phone to monitor/steer/approve/review, while Codex still runs on the machine that owns the workspace.

For this guide, that means you can do the “session supervision” part of Codex (follow-ups, approvals, diff review) without living in SSH.

Get set up:

Phone workflow: start a Codex session and keep it moving

1) Start the session from your phone

From your phone (app or mobile web UI):

  • create a new session
  • choose Codex
  • pick the machine that should run it
  • send your task

2) Use your phone for the supervision loop

From your phone you can:

  • read progress in the transcript
  • send follow-ups (“pause and explain what you changed”, “only touch these files”)
  • handle permission prompts depending on your mode
  • review diffs before you commit

3) Switch between terminal and phone (both stay live)

Since Happier 0.2.13 with Codex CLI 0.131.0 or newer on macOS/Linux:

When a Codex session is started through Happier, the native Codex TUI and the Happier app connect to the same running App Server thread. Both sides stay live at once:

  • Type a prompt in the TUI over SSH → it appears in the phone app
  • Approve a command from the phone → the TUI continues
  • happier attach <session-id> opens the TUI on a session started from the phone

This is shared control, not a handoff. The session doesn't stop when you switch surfaces.

Limits:

  • Shared control only applies to sessions started through Happier. If you started a thread directly with codex, Happier can't join it while it's running (Codex keeps one active writer per thread).
  • On Windows, in ACP mode, or with an older Codex CLI, control is exclusive: a message from the phone waits until the terminal turn reaches a safe boundary.
  • The machine running the session has to be online. Happier doesn't fix an offline machine or a provider outage.

When you're back at a laptop/terminal on the owning machine:

happier attach <session-id>

Resume inactive Codex sessions (what to expect)

Codex resume in Happier normally uses the default App Server path.

An inactive Codex session can be resumed when:

  • the session has valid Codex resume metadata
  • the current backend/machine combination supports resume (App Server by default, or ACP if explicitly selected)
  • any required machine dependency for the selected resume path is already installed

From CLI:

happier resume
# or
happier resume <session-id>

From phone/app/web:

  • inactive sessions accept input only if they’re resumable
  • sending a message triggers resume first

Permissions and modes (the short version)

If you’re getting blocked a lot on prompts:

  • start with Default
  • try Safe YOLO for less interruption
  • use YOLO intentionally, and review diffs afterwards

Troubleshooting

Symptom: Codex sessions won’t resume

Likely causes:

  • the session is on a backend path that doesn’t support vendor resume (common if you forced plain MCP)
  • required dependencies for the selected path aren’t installed

Fix:

  • prefer the default App Server path for resumable sessions
  • keep Codex authenticated and ready on the machine

Symptom: I can’t attach from the terminal

Likely causes:

  • you’re on a different machine than the one that owns the session
  • attach behavior differs by OS (tmux on Linux/macOS; Windows uses different host modes)

Fix:

  • run attach on the owning machine

FAQ

Is Codex continuity as stable as Claude?

It can work well, but the docs are explicit that Codex handoff/continuity is still less mature than Claude/OpenCode in some paths.

If you want the most stable cross-machine handoff today, prefer Claude/OpenCode; if you want Codex, keep auth and dependencies ready on the machines you care about.

mobilecodexsessionsworkflows
Last updated: 2026-10-26