[Bug]: Codex CLI no longer reads custom providers after recent upgrade

Open 💬 2 comments Opened Jul 14, 2026 by Arrow-Li

What version of Codex CLI is running?

codex-cli 0.144.4

What subscription do you have?

free

Which model were you using?

gpt-5.6-terra

What platform is your computer?

Darwin 21.6.0 x86_64 i386

What terminal emulator and version are you using (if applicable)?

iTerm2

Codex doctor report

not available

What issue are you seeing?

<img width="940" height="354" alt="Image" src="https://github.com/user-attachments/assets/80306fe9-2932-48fa-b537-1daaf7466357" />
After upgrading to the latest version of Codex, the CLI no longer reads or recognizes custom provider configurations. The CLI appears to ignore the custom provider settings entirely, either falling back to default providers or failing to execute properly.
v0.144.1 works fine

What steps can reproduce the bug?

  1. Define a custom provider in the Codex configuration.
disable_response_storage = true

model = "gpt-5.6-terra"
model_provider = "cs"
model_reasoning_effort = "high"
model_context_window = 1000000
model_auto_compact_token_limit = 900000

[model_providers.cs]
name = "cs"
base_url = "https://cs.net/v1"
env_key = "CS_API_KEY"
wire_api = "responses"
requires_openai_auth = false
  1. Upgrade Codex to the current version 0.144.4 or 0.144.3
  1. Run a CLI command relying on the custom provider

What is the expected behavior?

The Codex CLI should successfully parse and load the custom provider configuration from the settings, allowing the command to execute using the custom provider exactly as it did in previous versions.

Additional information

Current Codex Version (Failing): 0.144.3, 0.144.4

Previous Codex Version (Working): 0.144.1

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗