Codex CLI 0.168.0 lets users pick a default model provider for new chats
OpenAI's Codex CLI 0.168.0 adds a model provider browser to the TUI and a setting for the default provider used by new chats.
OpenAI's Codex CLI 0.168.0 lets users choose which model provider new chats use. The option sits under a Model providers entry in Sessions in the terminal interface. The release notes list the feature first under New Features and point to two pull requests.
The mechanism is split across two changes. Pull request #59541 added a browser. The Model providers entry shows the current chat's provider and the default for new chats, and it offers scrollable details for endpoints, authentication settings and provider-specific configuration. The pull request states that browsing does not change the active provider. Pull request #59722 added the ability to pick the default. Its description says pressing Space in the Model providers settings sets the default, and that the choice is saved as model_provider on the connected server. The same description says selection is disabled when server configuration or client launch settings fix the provider. A user whose provider is pinned elsewhere will see the entry but cannot change it.
The choice applies to /new, which starts a fresh chat while keeping the current one open. The second pull request also says the TUI blocks stale /model choices during saves and after provider changes, including across reconnects. Users are told to restart the app server and TUI to refresh the model list.
The changelog bug-fix entry covers the other half of the behavior. Pull request #59503, titled "Keep threads on their saved model provider when defaults change", is summarized in the release notes as open and resumed chats using their saved model provider after the default changes. In practice, changing the default affects only chats started afterward. Existing sessions keep the provider they were saved with.
The release also extends the app-server reference, which covers listing model providers, creating custom gateways, and updating gateway, Bedrock and GCP settings. Those entries correspond to pull requests #58845 and #58876, both by alexsong-oai. The release notes don't say which provider types beyond those named are supported, and the pull requests excerpted here don't list them.
What changed
Codex CLI 0.168.0 lets users choose a default model provider for new chats, saved as model_provider on the connected server, while existing chats keep their saved provider.
Type: New capability · Applies to: Codex CLI 0.168.0, model_provider
Why it matters
Teams that route Codex through gateways or cloud providers such as Bedrock or GCP can switch defaults without breaking existing chats.
What you can do
If your team uses custom gateways or cloud model providers with Codex, test the new default-provider setting on a sample project before rolling it out.
Original source
- github.comRelease 0.168.0 · openai/codex · GitHub
- github.comAllow choosing the default provider for new chats in the TUI by copyberry[bot] · Pull Request #59722 · openai/codex · GitHub
- github.comAdd model provider browsing to the TUI configuration panel by copyberry[bot] · Pull Request #59541 · openai/codex · GitHub
Where we saw it
Codex CLI releases
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works