4 people reported
All time, since Oct 10, including 3 thumbs-up on GitHub.
Workspace routing startup failure
“Setting log_dir at the top level of config.toml does not fix it, and temporarily removing config.toml entirely still fails.”
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/11329/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
Startup fails with workspace routing discovery error unless a -c override is passed. Plain codex fails during TUI bootstrap with a valid ChatGPT login and working proxy; passing an unrelated CLI config override lets it start.
Is this your bug?
File my report- Where
- CLI startup
- Error text
Error: account/read failed during TUI bootstrap: account/read failed: workspace routing discovery failed (code -32603)- Versions
- 0.156.1
- Platforms
- Linux
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Workspace routing discovery fails2 people
- Workspace routing startup timeout2 people
- Background server feature mismatch26 people
Original reports1, newest first
- CLI account/read workspace routing fails by default but succeeds with unrelated -c overrides (0.156.1–0.162.1)On GitHub#52928