Why you'd want it
opencodex is a local proxy that translates Codex's Responses API into whatever the provider speaks, covering streaming, tool calls, reasoning tokens and images. The README says it works with Codex, Claude Code, Claude Desktop and Grok Build, with 40+ built-in providers plus any OpenAI-compatible endpoint. A web dashboard on localhost:10100 is where you add providers, pick models and manage accounts, and it shows a live request log. Models are targeted with provider/model syntax such as codex -m "ollama/llama3", and combos give one virtual model id with failover or weighted round-robin across providers. ocx stop restores Codex to its original configuration.
Best for
- Running Codex on non-OpenAI models
- Using Claude Code with other providers
- Failover across providers with combos
Use it when
You want Codex or Claude Code to use another provider's model, including a local Ollama model, and you are fine running a local proxy with a dashboard.
Skip it if
The README warns that some providers, notably Anthropic, may suspend or restrict accounts that route traffic through third-party proxies, and says the project is independent and not affiliated with OpenAI or Anthropic. It handles provider API keys, OAuth logins and optionally a pool of ChatGPT accounts, and ocx init wires Codex to the proxy, so read AGENTS_INSTALL.md for what it writes to disk. The desktop app is labelled beta and the Cursor adapter experimental; the from-source route pipes a curl installer for Bun into bash, which the npm route avoids.
Editor's note
Other routes in the README: desktop app (beta), Docker Compose, install from source. Docs at opencodex.me.