Constant sqlite writes when using API key auth about no remote control support

[lattwood]

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.623.31921 • Released Jun 26, 2026

What subscription do you have?

API Key

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

> sqlite3 -readonly ./.codex/logs_2.sqlite 'select * from logs order by ts desc limit 10'
66298694|1782487142|422302000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298693|1782487141|420619000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298692|1782487140|418696000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298691|1782487139|416587000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298690|1782487138|414970000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298689|1782487137|412992000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298688|1782487136|410670000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298687|1782487135|408504000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298686|1782487134|406999000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356
66298685|1782487133|405072000|INFO|codex_app_server_transport::transport::remote_control::websocket|waiting to resolve remote control preference until authentication is available error=remote control requires ChatGPT authentication; API key auth is not supported|codex_app_server_transport::transport::remote_control::websocket|app-server-transport/src/transport/remote_control/websocket.rs|609||pid:98402:3d95747d-29a0-4e51-a155-d5bfac6bc982|356

What steps can reproduce the bug?

Use Codex app with API Key.

Look at sqlite.

What is the expected behavior?

It shouldn't do this?

Additional information

I stumbled onto this when trying to figure out why dictation didn't work with API Key auth

[Nicolas0315]

I pushed a candidate fix here:

https://github.com/openai/codex/compare/main...Nicolas0315:codex:codex/remote-control-api-key-log-throttle?expand=1

Commit: e353c9e0883597a649af610722b8464db472659d

The change keeps the existing retry behavior while the remote-control desired state is Unknown, but only emits the auth-resolution info! line when the (ErrorKind, message) changes. For the API-key case this preserves the first diagnostic and stops the one-row-per-second SQLite log growth from identical retries.

Local verification:

• just fmt
• git diff --check
• cargo test --manifest-path codex-rs\Cargo.toml -p codex-app-server-transport repeated_preference_resolution_auth_errors_log_once_until_error_changes
• cargo test --manifest-path codex-rs\Cargo.toml -p codex-app-server-transport plain_start_resolves_persisted_remote_control_preference
• cargo check --manifest-path codex-rs\Cargo.toml -p codex-app-server-transport
• cargo test --manifest-path codex-rs\Cargo.toml -p codex-app-server-transport (123 tests passed)

SSH verification:

• cyberagent-mac-m5max: fetched the exact commit, git diff --check origin/main...HEAD passed, focused cargo test passed after a fresh build (1 passed, build 4m41s).
• nicolas-macbook-pro: fresh scratch clone fetched the exact commit and git diff --check origin/main...HEAD passed; cargo/rustc are not installed on that host.
• rtx5060ti: fresh scratch clone fetched the exact commit and git diff --check origin/main...HEAD passed; cargo test is blocked by the host resolving the wrong link.exe for MSVC flags (link: extra operand ...).
• nicolas2025: fresh scratch clone fetched the exact commit and git diff --check origin/main...HEAD passed; focused cargo test timed out during a fresh dependency build after 5 minutes, and the scratch build cargo/rustc processes were stopped and verified absent.