Buttons All Grayed Out and Cannot Send: Codex Desktop
Quick fix
No confirmed fix. Verify the request path and protocol, enable local routing, and test a new session; official quota status may still limit Desktop.
Symptom
Section titled “Symptom”就是按钮变灰掉了，有额度的时候是正常的，你正常物流到第三方供应商，但是账号用完额度之后就按钮都变灰都发不出去The button simply becomes grayed out. It works normally while quota is available, and requests are routed to the third-party provider as usual. But after the account quota is exhausted, all buttons become grayed out and nothing can be sent.
The issue occurs when the ChatGPT Plus or official quota is exhausted: the send button in Codex Desktop becomes grayed out, and messages cannot be sent even when a third-party provider is configured in CC Switch. The discussion suggests that Desktop may still bind sessions to the official subscription status or official route. The issue remains open, with no maintainer-confirmed root cause or official fix.
Comments mention several related variants: requests may continue going to `api.openai.com`, old sessions may remain bound to an old endpoint, or the third-party relay may use Chat Completions while Codex is configured for Responses, causing a protocol mismatch. However, the original reporter had already enabled local routing and specifically encountered a disabled button, so these troubleshooting methods are not confirmed solutions for this Desktop issue.
First determine whether requests are still going to the official service or Codex Desktop has disabled the send button directly. The reporter in this issue experienced the latter.
Run `/status` in the `codex` CLI, check the current provider and `base_url`, and compare them with the host actually requested by Codex Desktop.
Confirm that the third-party relay protocol matches the Codex configuration. The relay may use `/v1/chat/completions`, while the custom Codex provider may be configured for Responses (`wire_api = "responses"`).
Enable local routing in CC Switch and test again. Some users reported that this routes requests through a third-party provider, but it is not confirmed to restore the grayed-out Desktop send button in this issue.
After switching providers, start a new conversation or branch from the old conversation into a new session to prevent the old session from continuing to use the old endpoint.
If the button remains grayed out in a new session after the official quota is exhausted, this issue currently has no confirmed solution. Wait for a future Codex or cc-switch fix.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 1 real issues
- Are requests still going to the official service, or are they reaching the relay but still being blocked by Desktop?
- The original reporter confirmed that the send button became grayed out after the official quota was exhausted, preventing requests from being sent. The issue contains no evidence that requests reached the third-party relay.
- Why can Codex Desktop switch accounts while the Codex CLI cannot?
- A user reported this difference, but the discussion did not confirm the specific cause. Another comment suggested that a Codex update caused the issue.
- Does enabling local routing solve the issue?
- One user said `chatgpt.app` began using the third-party provider only after local routing was enabled. However, the original reporter had already enabled local routing, and Codex Desktop still disabled the send button after the official quota was exhausted, so this is not a confirmed fix.
Related problems
Section titled “Related problems”This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.