Skip to main content
As of April 24, 2026, some Codex versions may not let you select gpt-5.5 directly when you use a custom API provider. This is a local model catalog limitation in Codex. It does not mean the BetterToken https://www.bettertoken.ai/v1 endpoint is unavailable. You can add a local custom-models.json file so Codex can recognize gpt-5.5, then reference it from ~/.codex/config.toml. If a later Codex version supports gpt-5.5 natively, prefer the built-in Codex setup.
Use the complete custom-models.json provided on this page. If you edit the file manually, keep the existing model entries and fields, and only change the model configuration you need.

Setup steps

1

Prepare the custom model config file

The custom model config path is ~/.codex/custom-models.json.
Download the complete model catalog:Download custom-models.jsonPut the downloaded file in the Codex config directory and name it custom-models.json.The downloaded file is the complete model catalog. The next step references it from the Codex config.
2

Reference the JSON file in Codex config

Open the Codex config file ~/.codex/config.toml, then add or merge the following config.macOS / Linux example:
Windows example:
model_catalog_json must be a local absolute path. In TOML double-quoted strings on Windows, write \ as \\.
3

Restart Codex

After changing the config file, stop the current Codex process and start it in a new terminal session:

Troubleshooting

If gpt-5.5 still does not work, check these items in order:
  1. model_catalog_json uses a local absolute path
  2. custom-models.json keeps the complete model catalog
  3. base_url is https://www.bettertoken.ai/v1
  4. wire_api is responses
  5. model_provider matches the provider id in [model_providers.custom]
If your Codex version already supports gpt-5.5 natively, remove model_catalog_json and return to the regular Codex setup guide.