claudexor
Eliminates quota constraints by pooling multiple AI coding subscriptions and enables consistent context sharing across tools, reducing context-switching over…
Multi-harness control plane for Claude Code, Codex, Cursor, and OpenCode: quota-aware rotation across multiple Claude/Codex subscriptions, shared thread context, and cross-model review.
- Rotate between multiple Claude subscriptions to avoid hitting daily usage quotas
- Share conversation context across different coding AI models for peer review
- Distribute code generation tasks across Cursor and Codex accounts for load balancing
Eliminates quota constraints by pooling multiple AI coding subscriptions and enables consistent context sharing across tools, reducing context-switching overhead and maximizing utilization across your coding assistant budget.
Engineering teams running high-volume code generation workflows across multiple AI coding platforms simultaneously.
https://github.com/razzant/claudexor
By razzant
How to Get It
claude plugins install razzant/claudexor
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me rotate between multiple Claude subscriptions to avoid hitting daily usage quotas
Trust Signals Auto-scanned
Community Pulse Active
Discussed on Hacker News
- Show HN: Claudexor – quota-aware routing for Claude Code, Codex, and Cursor — Hacker News · 4 pts
1 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 433 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
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): 433 GitHub stars; contributors unknown; last commit 0d ago; license MIT.