Skip to content

Third-party codex api connected, but the official plan is exhausted—Codex

Quick fix

Update to CC Switch 4.0 or the latest version. If the balance warning remains, provide reproduction details and logs, then reopen the issue.

Error output
接的第三方 codex api,但是官方的套餐用光了,会一直有这个提示
English translation

A third-party codex api is connected, but when the official plan is exhausted, this message keeps appearing.

CC Switch previously performed an implicit automatic query of the official subscription quota. Therefore, even when Codex used a third-party API, it could still show an insufficient balance message after the official plan was exhausted. The maintainer said v3.16.2 changed this to an official subscription quota template that is disabled by default and must be explicitly enabled, and closed the original issue on that basis.

However, the reporter later said the problem remained after both CC Switch and Codex were updated to the latest versions, so the user did not confirm that the v3.16.2 change was effective. The follow-up issue was closed after no new reproduction information was provided for a long time. The maintainer said 4.0 substantially refactored the related functionality and recommended updating and retrying, but the corpus contains no confirmation of a successful resolution.

  1. Update CC Switch to 4.0 or the current latest version, then use the third-party Codex API again and check whether the insufficient balance message still appears.

  2. If the problem remains, provide the CC Switch version, operating system, complete reproduction steps, and relevant logs or screenshots, then reopen the issue.

ToolCodex
Version3.16.1(受影响)
PlatformsmacOS
Why does the insufficient balance message remain after both CC Switch and Codex are updated to the latest versions?
The existing discussion does not identify a definite cause. The maintainer initially said v3.16.2 addressed the implicit automatic query of the official quota, but the user reported that the latest version still reproduced the problem. The related functionality was later refactored again in 4.0, so update and retest, then provide complete reproduction information.
What should I do if the message still appears after updating to 4.0?
Provide the CC Switch version, operating system, complete reproduction steps, and relevant logs or screenshots, then reopen the issue for the maintainer to reassess.

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.