codex executable with invocation-local Dari provider settings. Your existing Codex configuration is left intact.
A personal OpenAI subscription connected under Credentials serves your attributed requests only when the organization is on the Pro plan; otherwise the router’s own provider keys are used.
When your ChatGPT subscription hits its usage limit, Dari records the reset time OpenAI reports and stops sending it requests until then. If the router has a Subscription Fallback Model set for OpenAI, that model serves in place of the router’s OpenAI models on the router’s own credential (configured under each OpenAI model on the router’s Models & Keys tab with its own execution provider, credential, single thinking level, and Fast Mode; it runs on a different provider and does not have to be an enabled model); otherwise the router credential is used when that fallback is enabled, or the request is refused with the reset time. The Credentials page shows the hold, and Mark Available (or dari credentials subscription mark-available codex) clears it early.
Every following argument is forwarded to Codex:
/v1. The launcher selects dari/routing and disables unsupported reasoning summaries. Codex may still copy a global reasoning-effort preference into the request, but Dari treats that model-specific preference as automatic so the router can choose the reasoning level per request. Check Activity in the dashboard to see each selection.
Set DARI_ROUTING_API_KEY before launching to use an existing Routing key instead of the CLI-managed key.
Manual Configuration
If you do not want to use the launcher, create a Routing API key:~/.codex/dari.config.toml. The dari filename matches the profile name used below:
base_url at https://routing.dari.dev/{router_id}/v1.