Codex 0.149.0 · Custom provider 401
This may affect a custom provider after upgrading Codex. Check its saved authentication before replacing the API key.
A provider with `requires_openai_auth = false` and no explicit authentication may send requests without a key. This checklist covers providers that previously used a saved API key.
Codex 0.149.0: check an upgrade-related 401
After upgrading to Codex 0.149.0, a previously working custom provider may report `API_KEY_REQUIRED` or `401 Unauthorized`. If it relies on an API key saved in `auth.json` and has `requires_openai_auth = false`, check the authentication setting below.
Back up and open the configuration file
Quit the client and make a backup of `config.toml` before editing it in a plain-text editor. The default locations are listed below. If you set `CODEX_HOME`, use the file in that directory.
Update the active provider only
Find the provider ID selected by `model_provider`, then find its matching `[model_providers.<id>]` section. Change the existing `requires_openai_auth = false` line in that section to the value below. Keep the provider ID, Base URL, model, and other settings unchanged.
requires_openai_auth = true
Save, restart, and verify
Save the file, fully quit and reopen the ChatGPT client, then test a new conversation. If CC Switch manages the configuration, also check its saved provider settings so a later switch does not restore the old value.
If the error continues
Confirm that the active provider points to `https://reverix.ai/v1` and that its saved credential is a valid ReverixAI API key. Check key status, expiration, and the current client configuration. A 401 can have several causes, so this setting is not a universal fix.