Background server feature mismatch

“Background server has incompatible feature settings”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/9237/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 21 a week at the early-October peak. A workaround is known.

Shared background server blocks startup over api_key_model_discovery mismatch. Running plain codex shows "Background server has incompatible feature settings"; required value varies, and restart may be disabled as "not managed by Codex."

Is this your bug?

File my report

Where: Shared app-server
Error text: Background server has incompatible feature settings
Versions: 0.160.0 to 0.161.0
Platforms: Linux, macOS, Windows
How bad: Breaks a normal workflow. Some reports say it used to work.

Not quite your bug?

Deleted daemon directory blocks TUI3 people
Stale CODEX_CLI_PATH backend hang2 people
Stuck on startup splash7 people

Original reports5, newest first

Oct 9, 2026[TUI] “This server is not managed by Codex” obscures daemon ownership and safe recoveryOn GitHub#52642
Oct 8, 2026Codex CLI 0.161.0 blocks same-version shared app-server over api_key_model_discovery defaultOn GitHub#52085
Oct 8, 2026Codex CLI 0.160.0 automatically launches persistent managed app-server and updater (0.161.0) without explicit settingsOn GitHub#51961
Oct 7, 2026"Cannot use the shared background server: requires api_key_model_discovery" when logged in with ChatGPT (Windows)On GitHub#51891
Oct 7, 2026Background daemon auto-update drains active session and leaves daemon incompatible with current Codex clientOn GitHub#51763