Coding tools

Codex CLI

Codex CLI cannot connect to xKiro right now. This is not a configuration you can get right — the protocol it speaks is one this gateway does not serve yet.

Not supported yet

Codex CLI dropped support for the Chat Completions API. It now speaks only OpenAI's Responses API, which posts to /v1/responses — an endpoint xKiro does not serve. Every other tool on this page speaks a protocol we do serve.

What changed#

Codex used to let you pick the protocol with wire_api. Older guides — including an earlier version of this page — told you to set wire_api = "chat" for third-party gateways. OpenAI removed that:

wire_api now accepts one value, responses, and that is also the default when the key is omitted.
Configuring chat first produced a deprecation warning, then became a hard error in February 2026. It does not fall back.
OPENAI_BASE_URL and the base_url key change the address Codex talks to, not the protocol. There is no flag or environment variable that brings Chat Completions back.

So the config is not fixable from your side: pointing Codex at https://api.xkiro.com/v1 makes it POST to https://api.xkiro.com/v1/responses, and that returns 404.

If you saw the old instructions on this page

They were correct when written and are not any more. If you already added an [model_providers.xkiro] block with wire_api = "chat", Codex will refuse to start until you remove it — that startup error is Codex rejecting the setting, not a problem with your key or your network.

Remove this block from ~/.codex/config.toml (Windows: %USERPROFILE%\.codex\config.toml)

[model_providers.xkiro]
name = "xKiro"
base_url = "https://api.xkiro.com/v1"
env_key = "XKIRO_API_KEY"
wire_api = "chat"        # ← Codex now rejects this outright

What to use instead#

If you want an agentic CLI on xKiro today, these speak protocols the gateway serves and are set up in a couple of minutes:

Claude Code — closest in feel to Codex. Two environment variables.
opencode — terminal agent, one provider block.
OpenClaw — long-running agent with its own memory.

Will this be supported?#

It needs /v1/responses implemented on our side — a real endpoint, not a docs change. If Codex CLI matters to your workflow, tell us: we weight this by how many people ask.