How much quota left?

Giving agents their quota data with quota-axi


Yesterday, while introducing Codex to the blog, I mentioned quota-axi in passing. And then I realised, have I blogged about it? Nope, haven’t. Time to write one!

quota-axi is a project I found on GitHub due to… Google Discover surfacing it. Don’t judge me, my feed is weird. Anyways, it’s runnable via npx, so agents can do it, just after vetting the code. It does touch locally cached credentials after all, which is a bit scary! I don’t want to become part of a proxy network (via Simon Willison).

Thankfully it seemed safe, and the recommended install path was an agent skill. Didn’t know npm could just install an agent skill like that, but you learn something every day. Anyways, with it installed, Claude Code, and now Codex, can check their own quota. Which would be good, if it actually did check… unfortunately it doesn’t until I probe it directly. Still, it’s nice to have the capability! And it’s possible to overcome the reluctance with prompting, so that’s good. One idea I had, especially since the Pro plan’s session quota can be limiting, is asking Claude to do a long session that needs to be cut in half to fit - since quota-axi surfaces quota reset timings, and Claude Code has a local scheduler, I could technically leave it running overnight and come back to something finished. Haven’t tested it yet, but probably will blog about it when I do.