ID 01a063cd-83f1-7df1-a261-6607f02cacbc

What version of Codex CLI is running?

0.153.0

What subscription do you have?

pro

Which model were you using?

5.6-sol

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What terminal emulator and version are you using (if applicable)?

powershell

Codex doctor report

unexpected status 404 Not Found: Unknown error, url: https://chatgpt.com/backend-api/codex/responses, cf-ray: a3558efd4f820d00-EWR

What issue are you seeing?

after updating, codex cannot create new sessions (even /btw fails with 404)

codex --yolo
WARNING: Codex usage could not be checked; using normal Codex and avoiding automatic paid fallback. Codex rate-limit check failed: failed to fetch codex rate limits: GET
https://chatgpt.com/backend-api/wham/usage failed: 404 Not Found; content-type=; body=
╭──────────────────────────────────────────────────────────╮
│ >_ OpenAI Codex (v0.153.0) │
│ │
│ model: gpt-5.6-sol xhigh fast /model to change │
│ directory: ~\tudelu_dot_com │
│ permissions: YOLO mode │
╰──────────────────────────────────────────────────────────╯

Tip: Try the Desktop app. Run 'codex app' or visit https://chatgpt.com/codex?app-landing-page=true

⚠ MCP client for codex_apps failed to start: MCP startup failed: handshaking with MCP server failed: Send message error Transport
[codex_rmcp_client::event_notification_transport::EventNotificationTransport<rmcp::transport::worker::WorkerTransport<rmcp::transport::streamable_http_client::StreamableHttpClientWorker<codex_rmcp_client::ht
tp_client_adapter::StreamableHttpClientAdapter>>>] error: unexpected server response: HTTP 404: , when send initialize request

⚠ MCP startup incomplete (failed: codex_apps)

What steps can reproduce the bug?

Uploaded thread: 01a063cd-83f1-7df1-a261-6607f02cacbc

What is the expected behavior?

No response

Additional information

No response

No source files or tests are named. Start by reproducing v0.153.0 with codex --yolo in PowerShell on Windows and inspect the 404 responses for the responses, usage, and MCP initialization requests. Done means new sessions, /btw, usage checks, and MCP startup no longer fail with 404 errors.