Show HN: Claudexor – quota-aware routing for Claude Code, Codex, and Cursor

Claudexor is a Show HN project that routes work across Claude Code, Codex, and Cursor with quota awareness. The author built it after constantly switching agents when one subscription hit its limit, and after finding that each harness had its own flow with no clear winner among Codex, Claude Code, and Cursor. The goal is to treat those subscriptions as a single pool instead of separate tools that force manual context switches.

On the product side, Claudexor merges multiple provider subscriptions into one place and supports switching between them on the fly. It ships as a macOS IDE plus CLI, MCP, and plugins, so the same quota-aware routing can sit in an editor session, a terminal workflow, or an MCP-connected setup. The author’s own stack is four Claude Code subscriptions, three Codex subscriptions, and two Cursor subscriptions under that single control plane.

For engineers who already pay for more than one coding agent, the hard problem is not model quality alone but quota exhaustion mid-task. When a limit trips, work stalls while you re-open another product, re-establish context, and hope the next plan still has headroom. A router that knows which subscription still has quota reduces that interrupt cost and keeps the same task moving without rewriting prompts from scratch in a different UI.

The market context is a multi-subscription reality, not a single-vendor IDE bet. Many builders already hold overlapping Claude Code, Codex, and Cursor plans and still overspend on pure token billing when they blow past flat or capped usage. Claudexor sits in that gap: instead of picking one harness or paying for runaway token usage, it treats existing seats as capacity you can reallocate as limits approach.

The practical takeaway is concrete cost and ops control. The author reports about $15k monthly saved versus token-based overspend by pooling four Claude Code, three Codex, and two Cursor subscriptions through Claudexor. What to watch next is whether quota-aware multi-subscription routing stays a personal macOS tooling stack or becomes the default way teams run mixed agent harnesses without paying twice for the same coding session.