Codex Configuration

Local Codex access needs only a Passion8 URL, API key, and enabled Responses-compatible model. Use CC Switch to manage configuration, or write the files manually below. Restart Codex after saving and verify the test request in the dashboard. An OpenAI account or browser OAuth is not required.

#Passion8 model and current official models

Checked on 2026-10-11. Passion8 examples consistently use the deployment-backed gpt-6-sol, with a client context limit of 272000 and compaction threshold of 250000. Current official Codex documentation recommends gpt-6.1-sol where available. An upstream release does not establish that your Passion8 token has access. Use the model permissions shown in your console and recheck limits when changing models.

Configuration cleanup: disable_response_storage and approvers_reviewer are absent from the current official reference and have been removed. There is no direct replacement that guarantees equivalent behavior. Data retention follows provider policy; approvals use approval_policy and sandbox_mode. The old template also placed suppress_unstable_features_warning incorrectly under [features]; the unnecessary suppression is omitted. review_model, show_raw_agent_reasoning and model_supports_reasoning_summaries remain documented. The latter two only affect models that support the relevant behavior.

#Before configuring

The examples use gpt-6-sol. If it is not available to your account, replace the model setting with an enabled ID.

#Configure with CC Switch (recommended)

CC Switch manages Codex providers visually and writes auth.json and config.toml. The fields are the same on macOS and Windows.

model = "gpt-6-sol"
review_model = "gpt-6-sol"
model_context_window = 272000
model_auto_compact_token_limit = 250000

codex "Describe this project in one sentence"

#Manual configuration

Use this path if you prefer not to install CC Switch or want direct control of both files. Back up existing files before replacing them. The provider, model, base URL and context settings should match the CC Switch result.

mkdir -p ~/.codex
cat > ~/.codex/auth.json << 'EOF'
{
  "OPENAI_API_KEY": "YOUR_PASSION8_API_KEY"
}
EOF

cat > ~/.codex/config.toml << 'EOF'
model_provider = "Passion8"
cli_auth_credentials_store = "file"
forced_login_method = "api"
model = "gpt-6-sol"
review_model = "gpt-6-sol"
model_reasoning_effort = "medium"
model_context_window = 272000
model_auto_compact_token_limit = 250000
approval_policy = "on-request"
web_search = "live"
sandbox_mode = "workspace-write"
model_supports_reasoning_summaries = true
personality = "pragmatic"
show_raw_agent_reasoning = true

[model_providers]
[model_providers.Passion8]
name = "Passion8"
wire_api = "responses"
requires_openai_auth = true
base_url = "https://passion8.cc/v1"

[features]
goals = true
EOF
chmod 600 ~/.codex/auth.json

codex "Describe this project in one sentence"

New-Item -ItemType Directory -Force "$env:USERPROFILE\.codex"
@'
{
  "OPENAI_API_KEY": "YOUR_PASSION8_API_KEY"
}
'@ | Set-Content -Encoding UTF8 "$env:USERPROFILE\.codex\auth.json"

@'
model_provider = "Passion8"
cli_auth_credentials_store = "file"
forced_login_method = "api"
model = "gpt-6-sol"
review_model = "gpt-6-sol"
model_reasoning_effort = "medium"
model_context_window = 272000
model_auto_compact_token_limit = 250000
approval_policy = "on-request"
web_search = "live"
sandbox_mode = "workspace-write"
model_supports_reasoning_summaries = true
personality = "pragmatic"
show_raw_agent_reasoning = true

[model_providers]
[model_providers.Passion8]
name = "Passion8"
wire_api = "responses"
requires_openai_auth = true
base_url = "https://passion8.cc/v1"

[features]
goals = true
'@ | Set-Content -Encoding UTF8 "$env:USERPROFILE\.codex\config.toml"

codex "Describe this project in one sentence"

#Common checks

codex --version
codex "hello"

Check these when troubleshooting:

• The authentication field is exactly OPENAI_API_KEY.
• The base URL is https://passion8.cc/v1.
• The model is enabled for Codex / Responses on your Passion8 account.
• Custom routes should use their documented context/compaction settings.

Avoid conflicting active configurations. If CODEX_HOME is set, it determines the configuration directory. The fixed field name OPENAI_API_KEY holds your Passion8 key; this setup uses API credentials, not browser OAuth.

#Gateway Setup FAQ

#Does OPENAI_API_KEY need an OpenAI-issued key?

This is Codex’s fixed authentication field name; enter your Passion8 API key. The configured base_url sends requests to https://passion8.cc/v1. Local gateway access does not require an OpenAI account or browser OAuth.

#Can I enter any GPT model ID?

No. The model must be enabled for your token and support the Responses protocol used by Codex. Copy the exact ID from the dashboard and check context and compaction limits when switching models. A Chat Completions model that works in Cline may not work in Codex.

#Do I need to configure the VS Code extension separately?

A local extension and CLI share user-level configuration; see the Codex VS Code extension guide. Remote SSH, WSL, and containers read configuration in their own runtime environment, so check the actual user directory. To switch four vendors in one editor extension, see Cline multi-model configuration.

#Next steps