Coding Capacity
Early access / Concept stage

For developers using 2+ paid coding tools

Stop manually juggling coding-agent usage limits.

Checking quota windows. Switching tools. Pacing expensive tasks. Deciding which provider gets which work.

If you pay for Claude Code, Codex, Cursor or other coding tools, some of that may sound familiar.

I’ve been researching this problem. I’m testing whether a small tool would be useful enough to pay for. I haven’t built the product.

The outcome I’m testing

  1. 01 / UNDERSTANDKnow what’s availableA clearer picture of the usage and budget you have across your coding tools.
  2. 02 / PLANDecide where work goesPlan which provider handles a task and when it makes sense to run it.
  3. 03 / PACEFewer surprisesSpend less time manually checking limits and rearranging your work.

These are proposed outcomes. Provider integrations and feasibility still need to be checked. This page does not promise automatic switching, scheduling or hard spending limits. There is no launch date yet.

Is this for you?

You’re an individual developer, technical founder or small engineering team using two or more paid coding tools. Usage limits or budget decisions affect your work regularly, and you have a way of managing them today—even if it’s just checking each tool yourself.

What happens next

Tell me what you use, what you do now and what gets annoying. If native controls or a free tool already handle it, say that too. You can give feedback without asking for access. If you do want to try the concept, choose that in the form. I’ll use the responses to decide whether to take it further.

— Kai