Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Sessions → Model providers selects the new-chat default; open and resumed chats retain their saved provider.
- Side conversations require features.tui_workspace opt-in.
- Use user-level configuration for model_provider and model_providers; project-local copies of these keys are ignored.
Check a new chat after changing the default
OpenAI’s November 13, 2026 Codex CLI 0.168.0 notes add Sessions → Model providers for new chats. Open and resumed chats retain their saved provider. A provider is the service connection handling model requests; check it separately from the model name.
Keep separate observations for a genuinely new chat and a resumed one. Decide which you intend to change, then inspect its selection. Changing a default alone does not establish that an ongoing historical task switched. This is a CLI release; confirm the version used by desktop or editor sessions separately.
Opt into the side conversation with tui_workspace
Enable features.tui_workspace for a conversation beside the main chat. The release documents dragging the divider to resize it and using leader z to zoom the focused pane.
The current CLI reference says --enable enables a named feature for that invocation. Following that general syntax, codex --enable tui_workspace is a startup example for an authorized environment; it was not executed here. Check which pane has focus before typing so a message intended for the main task reaches it.
Put provider configuration in the right source
The configuration reference places user settings in ~/.codex/config.toml. Trusted projects can load .codex/config.toml, but project-local files cannot override machine-local provider configuration. model_provider and model_providers are ignored there. Inspect the user-level file when maintaining these keys instead of adding more copies to the project.
model_provider identifies the provider, model_providers defines connections, and model selects the model. Managed requirements can enforce a provider over local and session configuration. If a selection does not take effect, record the configuration source and organization requirements for an authorized maintainer. Exclude keys, authentication headers and complete private configuration from explanations, screenshots and tickets.
Verify the client, session and failure stage
Record the CLI version, host, launch method and configuration source in the terminal that actually starts the task. Change one setting, then inspect new and resumed chats separately. Keep the original configuration available for restoration. For remote execution, inspect the actual remote process; a local terminal version does not establish the remote version.
For command-line checks, the current reference defines -c key=value as an override for that invocation; --disable turns off a named feature for that invocation. After a temporary check, inspect whether persistent configuration still enables it. One verified launch does not establish that every future entry point uses the same setting.
The release also reports a Windows fix allowing other Codex filesystem I/O to proceed while local MCP servers are idle. Filesystem I/O means file reads and writes; the scope does not diagnose every Windows stall, timeout or save failure. Retain a redacted error, time and failure stage. Separate configuration selection, connectivity, tool initialization and file operations, and recover business requests with unknown results before retrying them.
Sources
Frequently Asked Questions
Does asking for another provider in a prompt prove it changed?
Use the actual client or supported configuration and session state as evidence. A written request alone supplies no interface that can change the setting.
Does this update establish a usage reset or regional eligibility?
The provider and side-conversation entries establish neither. Check applicable account, organization, pricing and regional rules separately. This CLI event has not been verified as fulfilling a particular day of Tibo’s announcement.