Anton Panasenko f4e6aa70e5 feat(remote-control): add daemon pairing command (#29913) ...

## Why

Users who run Codex remote control through daemon mode can keep the
daemon running, but they do not have a CLI path to mint the short-lived
manual pairing code needed to connect another device. Without this
command, they need to speak app-server JSON-RPC directly.

Related: #25675

## What Changed

- Added `codex remote-control pair`, which connects to the existing
daemon control socket and calls `remoteControl/pairing/start` with
`manualCode: true`.
- Kept the command non-lifecycle-mutating: it does not start, enable, or
restart the daemon.
- Human output labels the manual code as `Pairing code: ...`; `--json`
preserves the full pairing response.
- Added daemon socket-client, CLI formatting, and parser coverage.

## Verification

- `remote_control_client::tests::start_pairing_requests_manual_code`
verifies the daemon client sends `{ "manualCode": true }` and parses the
complete response.
-
`remote_control_cmd::tests::remote_control_pairing_human_output_labels_the_manual_code`
verifies the human-facing output.

f4e6aa70e5 · 2026-06-24 18:00:06 -07:00

History

..

src

feat(remote-control): add daemon pairing command (#29913)

2026-06-24 18:00:06 -07:00

tests

[codex] Initialize exec-server OpenTelemetry at startup (#25019)

2026-06-18 11:03:42 -07:00

BUILD.bazel

[codex] Move release platform rules into bazel package (#27321)

2026-06-10 19:45:29 +00:00

build.rs

Add WebRTC media transport to realtime TUI (#17058)

2026-04-08 10:26:55 -07:00

Cargo.toml

exec-server: default remote transport to Noise (#26245)

2026-06-15 17:39:00 -07:00