unexpected status 404 Not Found — Codex
Quick fix
Change requires_openai_auth for the custom provider in config.toml to false, then start a new session to avoid sending gpt-reserve.
Symptom
Section titled “Symptom”unexpected status 404 Not Found
Model "gpt-reserve" is not supported by any configured account in this groupAfter switching to a third-party custom provider in cc-switch 3.20.1, `requires_openai_auth = true` makes Codex treat that provider as an official authenticated route. When official quota is exhausted, the desktop client still uses account-level fallback and sends `gpt-reserve` to the third-party endpoint. That model is not in the third-party configured model group, so it returns 404.
Comments on the original post confirm that cc-switch forcibly writes this value on every apply for the built-in `cn_official` provider. The retained official `auth.json` and the official account status in the UI accompany this behavior, but the verified immediate workaround is to change the setting to `false`.
After switching to a third-party provider, change `requires_openai_auth` to `false` in `[model_providers.custom]` in `config.toml`.
config.toml [model_providers.custom]requires_openai_auth = truerequires_openai_auth = falseStart a new Codex session so requests use the provider model directly instead of triggering account-level `gpt-reserve` fallback.
Check this value after switching providers through cc-switch again; the original post says cc-switch writes it back to `true`, so change it back manually or use a script to correct it automatically.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 3 real issues
(No FAQ yet)
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.