‘Brought to You in 5-Hour Increments’: A Week of Moving AI Usage Limits

The thing people pay AI companies for is usage, and usage is measured by a meter. This week, across the coding-agent subscriptions in particular, the meter moved — and it kept moving. OpenAI brought back a five-hour usage cap for its Plus subscribers on the Work and Codex surfaces, having taken such a cap away earlier in the summer. Anthropic’s weekly quotas carried on resetting to their own rhythm. And a lot of people who had quietly built their working day around a number discovered, again, that the number is not theirs to rely on.

This is a Voices piece: a round-up of what actual users said, in their own words, in the past week. Quotes sourced from: Hacker News and GitHub. We opened each thread and lifted the wording verbatim; every quote is linked in the Sources list at the foot, with the handle, platform and date. As ever, we have kept the people who disagree in the room, because a round-up that only quotes the angry half is just a mood with citations.

The limit that came back

The spark was a reversal. A cap that had been lifted returned, and returning a limit lands very differently from never having removed it — you notice the wall more when you had got used to its absence. One user, monster_truck, put the whiplash drily: “it’s so fast that they’re slowly bringing back 5 hour limits”. Another, datakan, reached for the obvious deflation:

The most transformative technology ever created! Brought to you in 5 hour increments….. maybe

For at least one person the reinstated cap was not a philosophical matter but a wrecked afternoon. That is our moan of the day.

You can dismiss “forced to upgrade” as the standard complaint of a heavy user meeting the edge of a cheap plan — and we will steel-man exactly that in a moment. But the specific grievance, that the cap arrived mid-sprint and turned paid work into a dead stop, is the one that recurs all week in different clothes.

A number you can’t plan around

The sharpest version of the complaint is not “the limit is too low”. It is “the limit is unknowable”. A cap you can see and budget against is a constraint; a cap that moves is a source of low-grade anxiety. venzaspa caught the precise texture of it:

I used to think it was pretty great but now it just means you can’t plan your usage across the week. It’s a slightly entitled complaint but when you ‘waste’ 80% of your remaining usage because you get a reset you weren’t expecting, there’s a ping of disappointment there.

Note the self-awareness — “a slightly entitled complaint” — which is the tell of someone describing a real irritation rather than manufacturing one. The unpredictability runs in both directions. mbreese reported being “hit with limits at 4am Eastern time when I’d expect for not a lot to be going on”, having assumed quotas would at least track demand. And qsort pointed at the deeper opacity — that it is not only the allowance that shifts but what you get to spend it on:

They now give out resets you can choose when to use, but with a ‘best before’ date. With Anthropic you don’t even know what model you’ll have access to next week.

Over on the Anthropic side, Petersipoi described weekly usage that “gets reset CONSTANTLY” — “It’s crazy. The longest I’ve ever seen it go without a reset is maybe 5 days?” A generous reset sounds like a gift until you realise it means the quota you were pacing yourself against was never a fixed quantity in the first place.

Paying for something that can vanish

If the allowance is unstable, what exactly is being sold? svachalek wrote the week’s most cutting description of the model, and it is worth quoting at length because the escalation is the point:

Pay for “usage” that disappears arbitrarily: coded that bug fix for you, 3% usage consumed. Would you like to upgrade your plan to pro for “more” usage or max for “much more” usage? Buy pro max for “most” usage and access to our latest model, until we revoke it 15 minutes from now.

The mockery lands because it is not far off the lived experience: a currency you buy, spend and lose without a clear exchange rate. Two users independently reached for the same historical rhyme. mostertoaster asked whether “we look back at how AI usage is charged today and we equate it with how we had minutes on AOL and how absurd it seems looking back?” — and olyjohn sharpened it into an indictment:

At least minutes on AOL was honest. If it was today it would be “Unlimited AOL” with a limit of 10 hours, then throttle you back to 300 baud.

The casino in the machine

The most interesting thread of the week was not about pricing at all but about psychology — the suspicion that the unpredictable reset is not a billing quirk but a design. matheusmoreira made the accusation plainly:

If you see any sort of timer anywhere, you are in a Skinner’s box simulator. You are being subjected to positive and negative reinforcement via the reward schedule. This is habit forming.

Whether or not that is the intent — and intent is exactly the sort of thing we decline to assert without evidence — the effect he describes is real enough that others recognised themselves in it. And harrisoned supplied the cynical forecast that tends to accompany it: “It will get worse! Tighter limits, forcing people to higher plans. Most will go as they are addicted and dependent on those tools.” That is a prediction, not a fact, and worth holding lightly — but it is a prediction with a long SaaS track record behind it.

When the meter itself misfires

Underneath the philosophy sits a more mundane and more damning problem: sometimes the meter is simply wrong. On GitHub, a Claude Code user, ahmetbalaman, filed a bug report on 27 August describing a usage counter that moves on its own:

Immediately after my five-hour session resets, the “Current session” value jumps straight to around 50% without me sending a single message. It is not a gradual increase — it goes up in one step.

If the number can leap to half-spent before you have typed anything, then the debate about whether the limits are fair is almost beside the point — you cannot even trust the reading. A meter you are billed against ought, at the very least, to be accurate, and a steady trickle of reports like this suggests that is not always a given.

To be fair

Now the other half of the room, because it was genuinely there. Not everyone thinks the resets are a scandal, and the strongest counter is that a provider handing out free allowance is doing users a favour, not running a con. bko was blunt about it:

I think it’s great that oai resets users limits. What is this complaint? Free drinks? Keep customers happy? Reward your heaviest users? Casino vibes

And benmorris supplied the concession that any honest version of this piece has to include — that the raw value on offer remains extraordinary:

This sucks, but really the value of the $20 plan has been insane. I routinely get weeks of work out of the weekly limit, so yeah I’ll just move up plans if needed.

Both are right on their own terms. A twenty-dollar plan that does weeks of real work is a bargain, and a company that resets your quota to keep you happy is not obviously villainous. The complaint is narrower and, we think, sturdier than “limits bad”: it is that a limit you cannot see, predict or rely on is a strange thing to build your working life around, however good the underlying deal.

What to take from the week

If there is a practical posture in all of this, it is to stop treating the meter as a budget and start treating it as weather — something you plan around but never quite trust:

• Don’t reorganise your day around an expected reset. Several users described spending early to “beat” a reset that then did not arrive when they assumed. The reset is not a schedule; it is a surprise.
• Keep a lighter fallback for when a cap lands mid-task. The worst version of this is being stopped in the middle of something with no way to finish. A cheaper model or a second provider is insurance against the wall.
• Sanity-check the counter. If your usage leaps without input, you are not imagining it — it is a reported bug, worth logging rather than paying around.
• Be honest about what you’re paying for. If the pull is the compulsion to drain an allowance before it resets, that is the timer working on you, not a workload you actually have.

The limits themselves are defensible; renting time on someone else’s very expensive computers was always going to be metered. What grated this week was the instability — a cap removed and reinstated, quotas that reset on a whim, a counter that moves on its own. We have watched paying users spend the month asking, in one form or another, what exactly they are paying for, and defecting between coding tools in search of a better deal; this is the same discontent seen from the angle of the meter. It is not too much to ask that the number you are billed against sits still long enough to read. This is, after all, not the first time a reset has been turned into a lever — and it will not be the last.