Codex CLI Adds /rc and /remote Commands and codex exec --remote for Remote Control

CodexView original changelog

Codex CLI 0.171.0 adds /rc and /remote commands that manage local remote control and show device pairing codes inside the terminal interface. It also adds codex exec --remote , which starts or resumes noninteractive sessions on an existing app server. Together they make it easier to drive Codex from another device or from scripts against a running server.

Key Takeaways

  • /rc and /remote now manage local remote control and display device pairing codes directly in the Codex terminal interface.
  • codex exec --remote lets developers start or resume noninteractive sessions on an app server that is already running.
  • The additions give the CLI matching entry points for pairing devices and for scripted work against a shared server.
  • Pairing a device can now be started from inside the terminal session rather than from a separate flow.
  • The release also lets users choose and author custom MCP status lines through /statusline.
  • Bug fixes in the release include approvals no longer being cancelled by late completion events from an earlier turn.

Remote control from inside the terminal

Codex CLI 0.171.0 adds two commands to the terminal interface, /rc and /remote. They let developers manage local remote control and show the device pairing codes needed to connect another device to the running Codex session. Pairing steps that previously happened outside the terminal can now be started from the same place where the session is running.

Running noninteractive sessions on an existing server

The release also adds codex exec --remote . The command starts or resumes a noninteractive session on an existing app server instead of spinning up a new local one. Teams that keep a Codex app server running can send scripted or automated work to it. Sessions can also be resumed against the same server, which keeps work in one place.

Why it matters

Remote use of Codex has become a larger part of the product, with mobile apps that connect to a paired computer and app servers that hold long-running work. These two additions give the CLI matching entry points: one for people who want to pair a device, and one for scripts that need to reach a server that is already running.

Other changes in 0.171.0

  • Custom MCP status lines can be chosen and authored through /statusline.
  • Enterprise MCP sign-in now works for identity providers that issue ID tokens without refresh tokens.
  • Late completion events no longer cancel approvals for a newer turn.