codex-pooler
Centralizes multiple Codex accounts through a single gateway, reducing operational overhead and enabling load distribution across API quotas without managing…
Self-hosted gateway that pools multiple OpenAI Codex accounts behind stable Pool API keys. Clients send Codex-backend or OpenAI-compatible requests; the gateway routes each one to an eligible account based on model support, quota, limits, session continuity, and health. Deployed via Docker Compose with a Postgres database. Not a Claude tool.
- Route API requests across multiple Codex accounts to avoid rate limits.
- Manage dozens of Codex credentials through a single gateway interface.
- Distribute code generation workloads evenly among pooled Codex instances.
Centralizes multiple Codex accounts through a single gateway, reducing operational overhead and enabling load distribution across API quotas without managing separate endpoints in application code.
Development teams using multiple Codex accounts needing unified routing and quota management without code refactoring.
https://github.com/icoretech/codex-pooler
By icoretech
How to Get It
Docker Compose — see the 'Quick Start With Docker Compose' section of the repository README (runs the published release image with a local Postgres database)
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
After installing, paste this into Claude:
Help me route API requests across multiple Codex accounts to avoid rate limits
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 25 GitHub stars; contributors unknown; last commit 0d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 25 GitHub stars; contributors unknown; last commit 0d ago; license no license.