Codex CLI — coming soon

Preview the Redline custom-provider configuration for Codex. Responses API support is still being verified.

Coming soon. Responses API and multi-turn tool support are still being verified. Last tested: not yet verified · Tool version: pending.

Responses API is required

Codex uses wire_api = "responses". A working Chat Completions endpoint does not establish Codex compatibility. Do not depend on this configuration for client work until the status changes.

Custom-provider configuration

The preview profile keeps your existing default provider intact. Merge it into ~/.codex/config.toml. The key is read from the environment, not embedded in the TOML file.

TOML · configuration preview

# Merge into ~/.codex/config.toml; preserve your existing settings.
# Coming soon: Redline Responses API support is still being verified.
[model_providers.redline]
name = "Redline"
base_url = "https://api.redline-api.duckdns.org/v1"
env_key = "REDLINE_API_KEY"
wire_api = "responses"

[profiles.redline]
model_provider = "redline"
model = "redline-core"

# After compatibility is verified: codex --profile redline

After support is verified

Set REDLINE_API_KEY to an engagement key, start codex --profile redline, run a small authorised task and inspect the billed usage. This step becomes supported only after a tested version and date are published.

Official configuration reference

OpenAI’s Codex configuration reference documents custom provider fields. Redline is an independent provider; these hosted models are not OpenAI models.