Clicking “Add” has no response, Codex
Quick fix
Enter a non-empty OPENAI_API_KEY in auth.json (JSON) before adding, then change it back to {} afterward; the maintainer plans to remove this validation.
Symptom
Section titled “Symptom”点击“添加”并无什么反馈，但看不到第8个提供商，config.json 也并没有更新。Clicking “Add” has no response, but the eighth provider does not appear and config.json is not updated.
This is a feature request/validation issue: when adding a custom provider, an error may appear at the top of the interface and require scrolling up to see it. The reporter stated that `auth.json (JSON)` must contain `OPENAI_API_KEY`, or the provider is not added.
The maintainer explained that the current response format reads `OPENAI_API_KEY` and checks that it is non-empty; this key cannot be read when the provider uses the chat format. The maintainer planned to remove the check, but the original issue did not confirm that the change was completed.
When adding a custom provider, first set a non-empty `OPENAI_API_KEY` value in `auth.json (JSON)`.
auth.json (JSON) {"OPENAI_API_KEY": "any"}After adding it, if the value is not needed, change `auth.json (JSON)` back to an empty object.
auth.json (JSON) {}If there is still no response, scroll up to check for an error at the top of the page, and follow the source issue for progress on the maintainer removing the validation.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 1 real issues
- Is it possible to fix this?
- The maintainer said the issue is related to reading and checking that `OPENAI_API_KEY` is non-empty, and planned to remove the check; the original issue did not confirm that the change was completed.
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.