Skip to content

Enable Codex Live for mobile Remote Control sessions hosted by Linux CLI #35248

Description

@constantins2001

What variant of Codex are you using?

Codex CLI/app-server on Linux with Remote Control enabled, accessed from the ChatGPT mobile app.

What feature would you like to see?

Allow the existing Codex Live voice mode in the ChatGPT mobile app to attach to a Remote Control session whose host is the Codex CLI/app-server running on Linux.

Remote Control already works in this setup: the Linux workstation appears in the mobile app, and its Codex sessions can be opened and controlled with text. However, Live mode is unavailable for those sessions. The same user can use Live when the remote host is the Codex desktop app on a supported desktop platform, so the missing capability appears to be host/platform parity rather than a missing voice experience.

Expected experience

  1. Start Codex Remote Control on a Linux workstation.
  2. Open the connected workstation and an active Codex session in the ChatGPT mobile app.
  3. Start the existing Live mode from that remote session.
  4. Speak with, interrupt, redirect, and approve actions for the same running Codex thread.
  5. Keep the same objective, conversation, tools, terminal activity, approvals, and session state before, during, and after Live mode.
  6. Let the Linux-hosted task continue after the mobile Live conversation ends.

The phone should remain the audio client. The Linux machine only needs to host the existing Codex CLI/app-server session and tools; this request does not require a native Linux desktop GUI or Linux microphone support.

Concrete mobile use case

A Linux laptop or workstation may keep Codex running while the user is away from the keyboard or traveling, for example while the computer is safely stowed nearby during a car journey. In that situation, the natural interface is a hands-free Live conversation from the phone: ask for progress, clarify requirements, redirect work, or respond to a blocker without opening or typing on the computer.

Requiring a supported desktop app to remain active makes Live available mainly when the user is already near that computer. That is the moment when voice is least essential. Remote Control is most valuable when the user is mobile or away from the keyboard, so Live should follow the remote session rather than depend on whether its host is macOS, Windows, or Linux.

Why this matters

A Linux workstation may be the always-on development host, while a Mac or Windows computer is not always available. Remote Control already makes the Linux-hosted Codex session accessible from mobile, but the user currently has to keep a supported desktop host online solely to use Live voice. Enabling Live for the existing Linux Remote Control path would remove that unnecessary dependency.

Existing sandbox and approval policies should remain authoritative. Spoken instructions should follow the same permissions as text instructions sent through Remote Control.

Related issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIenhancementNew feature or requestremote

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions