CLI intermittently halts with `{"detail":"Bad Request"}` and requires manual resume

Summary

For roughly the last two weeks, Codex CLI has intermittently stopped mid-session and displayed only:

■ {"detail":"Bad Request"}

After this appears, the active work pauses instead of recovering or continuing. The failure is random and has occurred repeatedly during otherwise normal CLI use.

Steps to reproduce

1. Start an interactive Codex CLI session.
2. Work normally for an extended session, including tool calls and continued turns.
3. At an unpredictable point, the CLI prints the Bad Request response above.
4. Observe that the session stops progressing and requires a manual resume/retry or CLI restart.

Because the failure is intermittent, there is no single deterministic command that triggers it.

Expected behavior

• A transient API-side bad request should either be retried safely or return a useful, actionable error.
• The CLI should not silently pause the active workflow.
• Ideally the error should include a request/correlation ID and enough sanitized context to diagnose the rejected request.

Actual behavior

• The CLI prints only {"detail":"Bad Request"}.
• Ongoing work stops immediately.
• No request ID, failing endpoint, validation detail, or recovery guidance is shown.
• Manual intervention is required to continue.

Frequency / impact

• Repeated intermittently over approximately two weeks.
• Causes loss of continuity in long-running tasks and can leave background work waiting without a clear failure state.

Environment

• Codex CLI: 0.145.0
• macOS: 26.5.1
• Architecture: Apple Silicon (arm64)
• Shell: zsh 5.9

Suggested diagnostics

It would help if the CLI logged a sanitized request ID, response status/body, retry classification, and which request field failed validation—without exposing prompt or repository contents.

No private project data, prompts, credentials, or repository details are included in this report.

{"detail":"Bad Request"}