Claude Code-like remote control

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #25994

Powered by Codex Action

+1, I'm extremely disappointed in Codex' implementation of this. It feels like it was rushed just to check off some internal checkbox

I tried making a workaround, but there are other bugs/unsupported features that makes it impossible. My project runs on Linux, so I setup codex app server with remote control on a linux VM, then on a Windows VM I setup the Codex windows app with an SSH connection to the Linux VM. On the Codex Windows app I can see the remote SSH project, but if I connect them mobile app or codex app from my laptop, neither of these can see the SSH project (nor any other projects from the Windows App)

As a Linux-first Codex CLI user, I strongly support this request. The current limitation makes the mobile Remote Control feature effectively unavailable for users whose primary development environment is Linux.

Claude Code's model is much closer to the expected workflow: start remote control directly from the terminal session, open the mobile app, and continue the exact same session with synchronized messages and approvals. Requiring a macOS or Windows desktop app as an intermediary defeats the purpose for headless Linux machines, home workstations, VPSs, and server-first workflows.

The key feature request is straightforward: allow codex / codex remote-control on Linux to pair directly with ChatGPT mobile, without a desktop-app relay, while preserving the same live CLI session, approvals, diffs, test output, and terminal state.

For users who deliberately choose a terminal-first workflow, this is not a niche convenience; it is a major usability gap compared with Claude Code.

I've found that 0.143 added a new command "codex remote-control pair" that generates a pairing code and it works to pair ChatGPT mobile with Linux using this.

I've found that 0.143 added a new command "codex remote-control pair" that generates a pairing code and it works to pair ChatGPT mobile with Linux using this.

Thanks a lots ! Works great

macOS CLI user on Codex 0.144.5. codex remote-control pair generated a pairing code, but the ChatGPT mobile Remote screen offered no visible way to enter it; initial setup still required the desktop app and its QR flow.

The desired experience is to expose the current visible CLI session directly through codex --remote-control or /remote-control, with a URL or QR code, and synchronize messages, approvals, diffs, tests, and terminal output with ChatGPT mobile—similar to Claude Code.

@gtcuco-personal In the ChatGPT mobile Remote screen you can click the button "Pair manually instead" to enter the pairing code.

I strongly support this request.

Environment:

• Codex CLI: codex-cli 0.145.0
• Platform: Linux remote server
• Terminal: SSH terminal
• Feedback thread: 019fc4ef-8756-7c13-9b03-24a1df9866d1

The experimental commands:

codex remote-control start
codex remote-control pair

are useful, but the experience should be simplified to match Claude Code’s /remote-control workflow.

My desired workflow is:

1. Start a normal Codex CLI session through SSH.
2. While that session is already running, enter /remote-control.
3. Open the ChatGPT mobile app.
4. See the exact same active CLI thread, conversation history, tool activity, and approval state.
5. Send messages from either the SSH terminal or the mobile app and have them appear immediately on both.
6. Steer, interrupt, or add constraints to the currently running task from mobile.
7. Approve or reject actions remotely under the same permission policy.
8. Disconnect mobile access without ending or replacing the terminal session.

Remote Control should attach the mobile app to the same already-running CLI session. It should not create a separate conversation, require restarting Codex, or move execution into a different session owned by a background daemon.

This is particularly valuable for remote-server workflows. I often run Codex on a server through SSH, but I may need to leave my computer while a long task is running. I want to continue monitoring and talking to the same agent from the ChatGPT phone app without maintaining an SSH connection on my phone.

It would also be useful to provide:

• A /remote-control command directly inside the TUI
• A short-lived QR code or pairing code
• A visible connected-device indicator
• Mobile notifications when approval or input is required
• Bidirectional real-time transcript synchronization
• Reliable steering and interruption from mobile
• Automatic reconnection after SSH or mobile network interruptions
• Device listing and revocation
• Preservation of the working directory, environment, sandbox, permissions, and active task

Claude Code currently provides a smoother terminal-to-mobile experience. Codex already appears to have much of the required Remote Control infrastructure, but attaching mobile directly to an existing active CLI session would make it substantially more useful.

It would indeed be highly useful have remote on at at the conversation level.

Adding another user report from Codex CLI 0.149.0 on Linux (ARM64).

The key missing workflow is the ability to take over the currently open interactive CLI conversation from the ChatGPT mobile app, with bidirectional live synchronization:

1. Start and continue a task in the terminal.
2. Run a simple command such as /remote-control.
3. Open that exact in-progress conversation on the phone.
4. Read new output, send follow-up instructions, and approve actions from mobile.
5. Return to the terminal without creating or switching to a different task/thread.

Starting a separate Remote task from mobile is not equivalent, because it loses the continuity of the CLI session already in progress. Claude Code's remote-control flow handles this handoff very well and is a useful UX reference.

codex remote-control pair covers the "start a new remote task" case, but the thing several people are describing here — attaching to the session already running in your terminal, with approvals and output flowing both ways — is a different mechanism, and it's the one that's missing.

Disclosure: I work on CodeVibe, which does specifically this, so treat it as a "here's a workaround that exists today" rather than a recommendation from a neutral party.

It runs as a Codex CLI plugin on your machine. You keep working in the terminal as normal; the plugin relays that live session to an iOS/Android app — messages both directions, plus the interactive approval prompts, so you can approve or reject a file edit from the phone and the terminal continues. No SSH tunnel and no port forwarding; the desktop connects outbound to a relay, and session content is end-to-end encrypted between your machine and your phone, so execution never leaves your box.

Details, how it works, and the mobile apps: https://quantiya.ai/codevibe
Install (macOS/Linux, works fine over SSH): curl -fsSL https://quantiya.ai/codevibe/install.sh | bash

It's obviously not a substitute for first-party support — if Codex ships live-session takeover natively, that's strictly better. But if you need the workflow now, it exists.