Codex Error Messages: Exact Text, Where the Cause Sits, and the Fix

Also covered in this guide

• workspace routing discovery timed outCopy
  • Cause: your machine or config
  • CLI
  • Desktop app
  • Issue #57058
• Sign-in failed: workspace routing discovery timed outCopy
  • Cause: your machine or config
  • Desktop app
  • VS Code
• Error running remote compact task: workspace routing discovery failedCopy
  • Cause: several possible
  • Desktop app
  • Issue #56789
  • Issue #56997
• workspace routing discovery unauthorized (401)Copy
  • Cause: account or plan
  • CLI
  • HTTP 401
• duplicate workspace in routing discoveryCopy
  • Cause: account or plan
  • CLI

workspace routing discovery failed or timed out clears in most reports with a background-server restart; unauthorized (401) needs a new sign-in on that host.

Codex desktop blocks every message in Work mode when it has no ChatGPT sign-in. Switch the mode menu back to Codex, or sign in with ChatGPT to keep Work.

Also covered in this guide

• You've made too many phone verification requests. Please try again later.Copy
  • Cause: account or plan
  • Issue #25820
  • Issue #52808
• This phone number is already linked to the maximum number of accountsCopy
  • Cause: account or plan
• Phone number already in useCopy
  • Cause: account or plan
  • Issue #45647
• The phone number you entered is invalidCopy
  • Cause: several possible
• unsupported Codex auth method: apikeyCopy
  • Cause: account or plan
  • Desktop app
  • Issue #45317

Codex in the ChatGPT desktop app may require phone verification that email or an authenticator app can't replace. What each error means and the safe next step.

Also covered in this guide

• unsupported_country_region_territoryCopy
  • Cause: account or plan
  • CLI
• error sending request for urlCopy
  • Cause: your machine or config
  • CLI

A Codex token-exchange 403 is a refused authentication request. The full error tells you whether to repair callback access, check the client’s network, renew stored credentials, or stop for an access restriction.

Also covered in this guide

• Please contact your workspace admin to enable device code authenticationCopy
  • Cause: account or plan
• Your access token could not be refreshed because your refresh token was revoked. Please log out and sign in again.Copy
  • Cause: account or plan
  • CLI
• ChatGPT login is disabled. Use API key login instead.Copy
  • Cause: account or plan
  • CLI
• Port … is already in useCopy
  • Cause: your machine or config
  • CLI

On a server with no browser, run codex login --device-auth and enter the code on any device. If that is blocked, tunnel port 1455 over SSH or copy auth.json.

Also covered in this guide

• {"detail":"Unauthorized"}Copy
  • Cause: account or plan
  • HTTP 401

Signed in with ChatGPT and never set a key? That 401 came from OpenAI's September 25, 2026 outage. The URL and key text in the error tell you if yours differs.

Also covered in this guide

• Error: app server is running but is not managed by codex app-server daemonCopy
  • Cause: your machine or config
  • CLI
• host Job Object prevents daemon detachmentCopy
  • Cause: your machine or config
  • CLI
• warning: Model metadata for `gpt-6.1-sol` not found. Defaulting to fallback metadata; this can degrade performance and cause issues.Copy
  • Cause: your machine or config
  • CLI

The error doesn't prove your plan is excluded: on one Pro account, Codex CLI 0.158.0 got it and 0.159.0 worked. Check the ID, client, daemon, then the account.

Also covered in this guide

• 没用上 Codex 官方模型列表（登录超过 8 天没有刷新），改用自带列表Copy
  • Cause: gateway or relay
  • Issue #8728
• 刷新 Codex 官方模型列表失败: 读取响应失败: error decoding response bodyCopy
  • Cause: your machine or config
  • Issue #8966

In CC Switch Routing mode, Codex gets an empty model list and shows its bundled one, which has GPT-6.1 Terra only from 0.165.0. Go back to Direct and restart.

Also covered in this guide

• The 'gpt-5.5' model is not supported when using Codex with a ChatGPT account.Copy
  • Cause: the service
  • CLI
  • HTTP 400
• unexpected status 404 Not Found: The model `gpt-5.5` does not exist or you do not have access to it.Copy
  • Cause: the service
  • Desktop app
  • CLI
  • HTTP 404
  • Issue #43344
• unexpected status 404 Not Found: Model not found gpt-5.5Copy
  • Cause: the service
  • HTTP 404
  • Issue #26892
• Model metadata for `gpt-5.5` not found. Defaulting to fallback metadata; this can degrade performance and cause issues.Copy
  • Cause: your machine or config
  • CLI

ChatGPT "Model not found" since Oct 14 has no official cause: try a new chat or browser, then support. In Codex, gpt-5.5 retired; use gpt-6.1-sol.

`gpt-image-2` is documented by OpenAI; when Codex says the model does not exist, the right fix depends on the surface that returned the error.

Also covered in this guide

• stream disconnected before completionCopy
  • Cause: several possible
• Quota exceeded. Check your plan and billing details.Copy
  • Cause: account or plan
  • HTTP 429
• Error running remote compact task: exceeded retry limit, last status: 429 Too Many RequestsCopy
  • Cause: the service
  • HTTP 429
  • Issue #15468
• Automatic approval review failed: exceeded retry limit, last status: 429 Too Many RequestsCopy
  • Cause: several possible
  • HTTP 429
  • Issue #53324
• exceeded retry limit, last status: 500 Internal Server ErrorCopy
  • Cause: several possible
  • HTTP 500

“exceeded retry limit, last status: 429 Too Many Requests” is a 429 Codex couldn't classify, not your usage limit. First stop parallel chats and sub-agents.

Also covered in this guide

• Reviewer model is at capacityCopy
  • Cause: the service
• Error running remote compact task: Selected model is at capacityCopy
  • Cause: the service

“Selected model is at capacity” means OpenAI had no room to serve that model, not that you ran out of usage. Wait, try one other model, or start a new chat.

The exact ‘This content can't be shown’ banner is a cyber-safety signal, not a generic Codex crash. Preserve the evidence, verify authorization, narrow the defensive task, and escalate without sharing secrets.

Also covered in this guide

• The extension couldn't load its resources.Copy
  • Cause: your machine or config
  • VS Code
  • Since 26.803.x
  • Fixed in 26.810.41047
  • Issue #37458
• PendingMigrationError: navigator is now a global in nodejsCopy
  • Cause: your machine or config
  • VS Code
• View containers cannot be contributed to the Secondary Side Bar in Cursor. It is reserved for Cursor's agent UI.Copy
  • Cause: your machine or config

“Codex could not start — The extension could not start its user interface” on build 26.1021.22027: fixed in 26.1106.51428 (Nov 11, 2026). Update and reload.

Also covered in this guide

• Disabled by your organization or unavailable in your regionCopy
  • Cause: several possible
  • Desktop app
  • Issue #44721
  • Issue #27882
• The browser access host is unavailableCopy
  • Cause: your machine or config
  • CLI
  • VS Code
  • JetBrains
  • Desktop app
  • Issue #57641
  • Issue #55173
  • Issue #56928
  • Issue #58856
• Browser is not available: iabCopy
  • Cause: your machine or config
  • Desktop app

Browser on but Codex says it is disabled? Fully quit and reopen the ChatGPT app, continue in a new chat, then check Work preferences → Local browser use.

Also covered in this guide

• Error creating task: TimeoutCopy
  • Cause: your machine or config
  • Desktop app
  • VS Code
• invalid turn/start params: AbsolutePathBuf deserialized without a base pathCopy
  • Cause: your machine or config
  • Desktop app
  • Web
• failed to start turn: internal error; agent loop died unexpectedlyCopy
  • Cause: your machine or config
  • Desktop app
• Can't find variable: DisposableStackCopy
  • Cause: your machine or config
  • Web
  • VS Code
• no rollout found for thread idCopy
  • Cause: your machine or config
  • Desktop app
  • VS Code

“Error submitting message”, once “Error creating task”, is a Codex client banner: line 2 names the cause. On a new chat, Timeout often means a stuck MCP server.

Also covered in this guide

• Failed to load global stateCopy
  • Cause: your machine or config
  • Desktop app
  • Issue #52713
  • Issue #58397

Codex projects missing after an update or account switch are usually still on disk. Update to 26.1106.51428, fully quit, and back up .codex before re-adding.