Codex CLI Models and Providers: Configuration Explained

model is the model identifier sent to the server; model_provider selects a set of connection settings; wire_api determines the request protocol used by Codex. Just changing the model name will not automatically switch the server.

Compatible services may implement only part of the protocol. Actual verification of tool calls, streaming output, and error behavior should prevail. Don't equate "can return text" with full compatibility.

The CodeNodex CLI configures an OpenAI Responses-compatible provider for Codex and sets both the main and review models to gpt-5.6-sol. base_url uses the public API endpoint, while the API key is stored separately in the authentication file.

Manually copying the configuration can easily miss authentication or overwrite existing fields. For production use, run codenodex setup first. The snippet below is for understanding the structure and does not contain secrets.

Automatic setup obtains the public base URL, validates the selected API key, then merges config.toml and auth.json. It aborts if the existing TOML cannot be parsed, preventing a silent overwrite.

The provider transport configuration is different for normal Codex and WebSocket variants. Current WebSocket variants only use supports_websockets and the removed responses_websockets_v2 feature is no longer enabled.

Put stable defaults in config.toml and use -m for temporary comparisons. Do not rely on interactive model selection in team scripts because it makes results difficult to reproduce.

Reasoning effort affects latency, cost and task performance. Increase it for difficult analysis; small mechanical tasks may not need the highest setting. The current configuration reference defines the available values.

review_model allows review work to use an independent default model. It must still belong to the collection of models recognized by the current provider; the availability of the main model does not mean that the review model configuration must be correct.

When assessing review quality, fix baseline branches, prompts, and code samples, and record real defects and false positives found, rather than just comparing answer lengths.

401 usually points to credentials or authentication headers, 404 may be a base URL path error, an unknown model indicates that the connection was made to the service but the model name does not match, and a protocol field error may manifest itself as a parsing or streaming response exception.

First use doctor and the CodeNodex key status to verify the local setup, then capture the provider fragment and error code with credentials removed. Never disable TLS verification or print complete request headers for troubleshooting.