Allow attaching the Codex terminal TUI to an existing Remote Control chat #32445

What feature would you like to see?

Please add a supported way to open or attach the Codex terminal TUI to an already-running Codex Remote Control chat/thread.

A typical workflow is:

1. Start codex remote-control on the Mac.
2. Open and continue a Codex chat from iPhone/iPad.
3. Return to the Mac and continue the exact same live chat in the terminal TUI.

At present, codex remote-control exposes only start, stop, and pair. There is no apparent attach, resume-remote, or equivalent command. codex --remote <ADDR> connects to an app-server endpoint, but does not provide an obvious way to attach to the existing Remote Control thread.

Why this matters

Remote Control is most useful when the same development session can move seamlessly between mobile and terminal. Without terminal attachment, the user must either remain in the app UI or start/resume a separate CLI session, which breaks continuity and may risk parallel or divergent work on the same repository.

Suggested interface

Any of these would solve the problem:

• codex remote-control attach
• codex resume --remote
• a session picker showing active Remote Control threads
• a stable thread/session ID that can be passed to the terminal TUI

The terminal should attach to the same live thread rather than create a duplicate continuation.

Environment

• macOS 26.5.2
• Codex CLI 0.144.1
• Remote Control used between Mac and iPhone/iPad