What's this about?
Someone burned their Claude quota in ten minutes, wanted to know what consumed it, and built a tool to break it down. Its README asks the question that gives the tool its purpose: "Is it safe to start a big refactor now, or should I wait for my window to clear?"
What is a "usage window"?
Subscription AI coding tools meter usage over a rolling period rather than per-request. You get an allowance, it refills on a schedule, and if you exhaust it you wait. The practical consequence is that starting a large task becomes a bet on remaining budget — and unlike a bank balance, most tools show you very little about what actually spent it.
What's the community saying?
HN 67 points, 53 comments — mostly jokes, with a real argument underneath
- The top comment is a deadpan "I didn't know it was still possible to develop software after your AI quota runs out", which sets the tone for a long Star Trek reference chain.
- The genuine disagreement inside the joking: someone argues AI isn't much faster for good code because review time roughly equals writing time, putting the productivity gain around 20%.
- The reply that lands: the size of the boost depends entirely on how much you care about code quality — if you don't need to understand the output, you get a lot of functionality fast.
- A pointed aside about incentives — "no one is vesting anymore, they just burned their quarterly token quota in 10 days."