Repository navigation
Seamless Codex Session Handoff Between CLI, Web, and Mobile #40124
Description
What variant of Codex are you using?
CLI
What feature would you like to see?
Codex should support seamless session handoff between CLI, web, and iOS.
I want to start a normal codex session in my terminal, leave my desk, open ChatGPT/Codex on my phone or the web, and continue the exact same session — including context, running processes, approvals, diffs, and terminal state — then return to the CLI later. Claude Code’s remote/session continuation sets the expectation here. Requiring the ChatGPT desktop app to be the session host makes Codex Remote considerably less useful for CLI-first developers.
Maybe related: https://github.com/openai/codex/issues/33948?utm_source=chatgpt.com
Additional information
No response
Activity
github-actions commentedon Aug 22, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
hendryyeh commentedon Aug 22, 2026
The CLI-side half of this — leaving your desk mid-session and picking the same session up on a phone, with approvals and diffs intact — is available today via a third-party plugin, if it's useful before first-party support lands.
Disclosure: I work on CodeVibe. It installs as a Codex CLI plugin, relays your running terminal session to iOS/Android with bidirectional messages and approval prompts, and needs no SSH tunnel or desktop app as host — which is the specific constraint you flagged. Content is end-to-end encrypted; execution stays on your machine.
What it does not do is the web leg of your request, or restore terminal state — it attaches to the live session rather than serialising and rehydrating it, so it's a narrower thing than what you're asking for.
Details and mobile apps: https://quantiya.ai/codevibe
Install (macOS/Linux):
curl -fsSL https://quantiya.ai/codevibe/install.sh | bashWorth noting the bot flagged #40055 and #38963 as possible duplicates — might be worth consolidating so the request carries more weight in one place.
weathon commentedon Aug 26, 2026
Update: if I pair both devices using method in this thread, it seems like I can use it without creating a ghost thread anymore.
bobfang1992 commentedon Aug 31, 2026
Strong +1. My workflow is CLI-first: I want to start a normal Codex session in the terminal, leave the machine, continue that exact live session from mobile, and later return to the CLI without losing state. Claude Code's remote/session handoff makes this feel like a major product gap rather than a nice-to-have.
barcuchj commentedon Sep 3, 2026
Related, but not an exact duplicate: this issue focuses on resuming the same live Codex session across CLI, web, and mobile, including approvals, diffs, running processes, and terminal state.
A separate but adjacent workflow is ChatGPT conversation → new or continued Codex task. That handoff needs selected messages, attachments/screenshots, provenance, and an explicit permission summary (read-only vs. modify, network, secrets, branch/PR), with structured status and results returned to ChatGPT. That is the focus of #40142.
A shared first-party session/task identity and explicit import/resume protocol could support both use cases without merging the underlying histories or permission models.
yhg0112 commentedon Sep 17, 2026
[Withdrawn.]