A Rust gatekeeper for your pile of Codex accounts

What it does It’s a self-hosted proxy gateway for OpenAI’s Codex: you register multiple upstream accounts, group them however you like, and hand out client API keys that can see only the groups you choose. A built-in admin panel shows system overview, account groups, proxy management, and usage statistics. It ships as a Docker Compose stack with PostgreSQL and Redis, and there’s a public demo instance with mock data if you want to poke at the UI before deploying.

The interesting bit It speaks the Responses API only — no /v1/chat/completions — so it’s aimed squarely at Codex CLI and desktop users rather than generic chat clients. There’s also a plugin system with an SDK and packaging tool, which is more extensibility than most proxy projects bother with.

Key highlights

• Multi-account pooling with per-key group scoping; a key with no group can use all accounts
• Admin panel with usage stats, plus a separate API-key-holder view for quotas and Codex config export
• Client onboarding via copy-paste config or CCSwitch import
• Plugin architecture with documented SDK and plugin CLI
• Apache 2.0, CI-gated releases, published container images

Caveats

• Responses API only — chat-completions clients won’t work
• The default bind is localhost; remote access needs your own HTTPS reverse proxy
• The README is thin on the “low risk-control” claims in the repo description — no details on how that’s actually achieved

Verdict Worth a look if you juggle several Codex accounts and want centralized keys, quotas, and stats. Skip it if you need a general-purpose OpenAI-compatible proxy — the Responses-only restriction is real.