XAI Router Codex Monthly Service: Codex / OpenCode

Posted February 14, 2026 by XAI Technical Teamย โ€ย 2ย min read

XAI Router now keeps the Codex story on one clean rule: Codex CLI / App stay on native Responses; OpenCode / Chat / Claude and other clients use their matching compatibility layers.


What Is Supported

  1. Codex CLI / App: native Responses path through https://api.xairouter.com.
  2. OpenCode: gpt-6-astra keeps its Responses request shape whenever possible through a targeted compatibility path.
  3. Compatibility APIs: /v1/chat/completions and /v1/messages still work, but they are bridge layers rather than the native Codex entry path.

Short version: Codex CLI / App should use /v1/responses; other clients should use their recommended integration path.


This is a recommended ~/.codex/config.toml example:

model_provider = "xai"
model = "gpt-6-astra"
model_reasoning_effort = "xhigh"
plan_mode_reasoning_effort = "xhigh"
model_reasoning_summary = "none"
model_verbosity = "medium"
approval_policy = "never"
sandbox_mode = "danger-full-access"

[features]
api_key_model_discovery = true

[model_providers.xai]
name = "OpenAI"
base_url = "https://api.xairouter.com"
model_catalog_url = "https://api.xairouter.com/models"
wire_api = "responses"
requires_openai_auth = false
env_key = "XAI_API_KEY"
supports_websockets = false
http_headers = { "x-codex-routing-hint" = "model=gpt-6-astra" }

Remote model discovery requires a CLI/App version that supports both settings. Restart after updating; see native model discovery.

Once this is in place, both Codex CLI and Codex App can point directly at https://api.xairouter.com. Here env_key = "XAI_API_KEY" only tells Codex which environment variable to read; on Linux use ~/.bashrc, on macOS prefer ~/.zshrc, and on Windows use a user environment variable before reopening the shell. On some older macOS setups, legacy terminals, or IDE sessions that still inherit a bash login environment, also mirror the variable into ~/.bash_profile, and into ~/.bashrc if needed.


Minimal API Examples

curl https://api.xairouter.com/v1/responses   -H "Authorization: Bearer ${XAI_API_KEY}"   -H "Content-Type: application/json"   -d '{
    "model":"gpt-6-astra",
    "stream": false,
    "input":[
      {"type":"message","role":"user","content":[{"type":"input_text","text":"Summarize today's task priority in one sentence."}]}
    ]
  }'

Chat Completions (Compatibility Bridge)

curl https://api.xairouter.com/v1/chat/completions   -H "Authorization: Bearer ${XAI_API_KEY}"   -H "Content-Type: application/json"   -d '{
    "model":"gpt-6-astra",
    "stream": false,
    "messages":[{"role":"user","content":"Give me one short weather suggestion for Shanghai today."}]
  }'

Claude API (Compatibility Bridge)

curl https://api.xairouter.com/v1/messages   -H "x-api-key: ${XAI_API_KEY}"   -H "anthropic-version: 2023-06-01"   -H "Content-Type: application/json"   -d '{
    "model":"gpt-6-astra",
    "max_tokens": 256,
    "messages":[{"role":"user","content":"Summarize today's task focus in one sentence."}]
  }'

Compatibility APIs are useful for existing integrations, but if you want the closest path to native Codex behavior, Responses remains the baseline.


OpenCode

For OpenCode, see: /en/blog/opencode-xai-router/. The current gpt-6-astra setup already keeps OpenCode on its Responses request shape whenever possible.


Conclusion

The current line is straightforward:

  • Codex CLI / App: prefer native Responses
  • OpenCode: prefer its recommended Responses integration
  • Chat Completions / Claude-compatible APIs: still available, but positioned as bridge layers
  • Codex config.toml in docs: unified to the current real local gpt-6-astra config