Does Codex CLI need a plugin or a fork?

No. Codex speaks the Responses API; the router serves /v1/responses on the same key. The router is a standard endpoint; the tool is unchanged.

Which model does the tool get?

Whatever it asks for. The name auto lets the router choose per turn under your policy; a model id pins it and still routes among its providers; a workspace alias maps the tool's own default name to either.

What does the router add that the tool does not have?

Codex on models OpenAI does not sell: the router executes on whatever provider the policy allows. A spend limit per key, so an agent loop cannot run away with the month's budget. Tool calls and their results on the trace, next to the price of each turn.

Can I use my own provider keys?

Yes - connect them under Model providers and the router executes on your accounts; model usage is billed by the provider, the platform meters requests.

Codex CLI through the router

Codex CLI, pointed at the router. Any provider behind it; your rules in front.

OpenSmartRoute serves the Responses API Codex CLI speaks, so one environment variable puts it behind your policy: the model it asks for can be auto, a budget caps what a developer spends, and every call lands in the trace with its cost and the alternatives.

Codex on models OpenAI does not sell: the router executes on whatever provider the policy allows
A spend limit per key, so an agent loop cannot run away with the month's budget
Tool calls and their results on the trace, next to the price of each turn

Create a free account Codex CLI docs

One commandbash

pip install opensmartroute
osr login                      # once: a browser sign-in, or --token osr_live_...
osr run codex          # Codex CLI starts with the router as its endpoint

Or by hand - codexbash

export OPENAI_BASE_URL=https://api.opensmartroute.ai/v1
export OPENAI_API_KEY=$OSR_API_KEY
codex --model auto

Codex CLI speaks the OpenAI API; the router serves chat completions and the Responses API at /v1 with streaming, tools and structured output passed through.

Verify

The first turn is on the activity page.

Send one message from the tool and read the row: the model that answered, the cost, the confidence and a link to the full trace with the alternatives and the policy decisions.

verify.shbash

# the tool's next turn is on the activity page with its cost, model and trace
curl -s https://api.opensmartroute.ai/api/v1/activity?limit=3 -H "Authorization: Bearer $OSR_API_KEY"

Questions

Codex CLI and the router

Does Codex CLI need a plugin or a fork?: No. Codex speaks the Responses API; the router serves /v1/responses on the same key. The router is a standard endpoint; the tool is unchanged.
Which model does the tool get?: Whatever it asks for. The name auto lets the router choose per turn under your policy; a model id pins it and still routes among its providers; a workspace alias maps the tool's own default name to either.
What does the router add that the tool does not have?: Codex on models OpenAI does not sell: the router executes on whatever provider the policy allows. A spend limit per key, so an agent loop cannot run away with the month's budget. Tool calls and their results on the trace, next to the price of each turn.
Can I use my own provider keys?: Yes - connect them under Model providers and the router executes on your accounts; model usage is billed by the provider, the platform meters requests.

Other tools

The same router behind every tool the team runs.

Put Codex CLI behind the router today.

A free account, one key, one command. Every turn the tool makes is priced, governed and explained from then on.

Create a free account Migrating application code instead?

Free plan, no card. Fifteen thousand decisions a month with the full trace.