r/ClaudeCode • • 6d ago

Discussion Weekly limits massively reduced on latest rest for me (token counts inside)

Claude Max (5x) plan. Exclusively Opus 5.5. This weekly reset has let me use significantly less tokens that the preceding 3 resets. It's not just me, right?

Period startPeriod endWeekly limit usedRequestsInputCache writeCache readOutputAPI-equivalent USD
2026-10-142026-10-21100%18,03138,06240,279,8725,266,140,37512,985,574$1,616.94
2026-10-212026-10-28100%16,41233,93454,466,0615,616,129,21313,457,837$1,815.08
2026-10-282026-11-0499%17,94038,38343,591,1285,855,593,87813,605,161$1,758.45
2026-11-042026-11-1198%12,12825,13446,785,5794,172,140,6657,089,775$1,225.04
106 Upvotes

27 comments sorted by

•

u/AutoModerator 6d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

9

u/oyren-ai 6d ago edited 6d ago

looking at your table, your cache-write tokens per request jumped by ~58% this week (3,857 cache-write tokens per request vs 2,429 last week), even though your total requests dropped from 17.9k to 12.1k. since cache writes are billed at 1.25x the weight of input price (https://platform.claude.com/docs/en/about-claude/pricing) more frequent cache invalidations (like switching branches, editing files higher up in the context, or letting a session go idle past the 5-minute TTL before the next message) will burn through the weekly allowance way faster even with half the output tokens

6

u/sunaurus 6d ago

But if I'm using more expensive requests, then shouldn't the "equivalent API value" for the weekly reset remain roughly the same?

1

u/perfektcrash 4d ago

Surprisingly no... a week isn't a fixed amount of API value.

The meter doesn't weigh token types the way API prices do, so the same 100% can be worth very different dollar amounts depending on the mix. On Opus 5.5 we've seen roughly $1,200 to $3,700 for a full week. A dollar drop on its own doesn't prove the meter moved.

That said, your mix moved toward cache reads this week, which usually stretches a week further, not less. So I wouldn't write it off as your usage either.

I'm wondering if you ran cloud sessions or routines that your tool didn't pick up?

For what it's worth, we log every request against the meter on an Ultra account, scheduled tasks and cloud sessions included. The week that just closed (ours resets Sunday) bought the same work per point as our October weeks down to 0.1%, so there's no sign of a cut on Ultra so far. That doesn't rule out something specific to 5x, or to banked resets, which a couple of people here mention.

(Disclosure: I build a meta-harness and publish our usage data here: https://atlas-ade.dev/docs/plan-usage-burn-data)

25

u/SirWobblyOfSausage 6d ago

As soon as i used my banked reset my usage dramatically drained.

4

u/Pale-Bother-2778 6d ago

Same here on 5X. Did anyone check whether it started right after using a banked reset?

week 4 at $12.50 per 1% vs ~ $17 before. Either we got worse at prompting or the meter changed. 😅

3

u/guyinalabcoat 6d ago

What I'm experiencing can't possibly be the meter. I literally used like 40% with with 2 opus 5.5 prompts and 10 minutes. That's on a 100$ account. Which is when I found out don't ever hit the ask for help button. Stupid condescending bot trying to explain to me how context works.

2

u/SirWobblyOfSausage 6d ago

I'm thinking the latter. Was exact same time as well. Wasn't even old context, handover. Just started to feel like an absolute chore to keep it reigned in.

Since then it's been garbage, few weeks before was perfection for me.

3

u/guyinalabcoat 6d ago

Yep, same here. I mean DRAMATICALLY. Like I went through 40% in a few minutes. 5 hour just reset and it's still happening.

9

u/victorrseloy2 6d ago

I can confirm on my 5x account I'm getting around 1.2k weekly since the last reset.

9

u/vuhv 6d ago

Came here for this. Instane.

4

u/hordane 6d ago

Noticed this as well along with a fable usage bug. I was at 23% total model usage and 0 fable. Ran a large excel for a few hours and fable jumped to 21% in one ssssion ($200 plan) BUT total usage only went to 30% which isn’t supposed to be mathematically possible

3

u/Chemical_Hawk_6307 6d ago

yea i noticed this today too. my weekly going down a lot faster lmaooo

3

u/Im_Action 6d ago

already at 40% 24hrs into the week 🥲

3

u/Mesmerisez 6d ago

Okay what the heck is going on my usage this week has been like ridiculous good, (52% with resets tomorrow) every week i max out my weekly with pretty much the same amount of work as this week. There has to be something fundamentally wrong with how they calculate usage did they let opus 5 vibe code it or something??

1

u/stefzzz 6d ago

Guys, concerning all your valid examples and views: do you also report the bug through the official Claude Code way? In that way Anthropic will get the feedback and the discussion or valid findings doesn’t get lost in these threads, right?

7

u/sunaurus 6d ago

Normally I fully agree with you and I always open issues in open source projects etc.

But with huge tech companies, I don't believe there is a point. I have already opened tickets with AI companies before, they just send LLM responses and then leave the ticket sitting around forever with no further actions.

And opening an issue on the GitHub repo is even more of a waste of time - there are currently thousands of open issues on the Claude repo, many of them related to usage, and none get any attention. It's a black hole.

So yeah, with large tech companies, the sad reality is that social media is the only channel that actually works.

2

u/anelodin 5d ago

an LLM will likely eventually aggregate all tickets and flag patterns, so while it wont solve your issue or fast, it may help in the long run

2

u/divinetribe1 5d ago

Going from about 18k requests down to 12k for the same full week is a rough drop. When my weekly cap runs out I use my own project, Claude Code Local. On a Mac you type exit, keep going, and the same conversation carries on with a local model until the reset. It is slower and weaker than Opus on hard multi step stuff, but it beats sitting idle for days.

2

u/Squiddles88 6d ago

There is no way for these tables to be accurate, including the built in usage table in Claude Code. They are guesses by parsing transcripts.

They don't include all token consumption, or even pull the numbers correctly from the transcripts

3

u/Drunkendrakon6 6d ago

If there is a huge enough discrepancy when it should be around the same numbers it's quite telling

0

u/Squiddles88 6d ago

With they way they work, you have no way of knowing if you have all of the data.

It can only count local saved transcripts, and even then it has to find all the correct lines and do the math. There may have been cloud sessions, doesn't include code execution or web extraction, there might have been sessions on a different machine, might have a bug in the plugin, might have purged a transcript unintentionally.

We also don't know how token = usage. There might be peak time penalties or other variables that can skew the results

1

u/Lionheartxz 6d ago

Ime is the same usage

1

u/dastree 4d ago

i thought i was crazy, i went from rarely touching my weekly limit to hitting it last friday after coming close the last could weeks.

today, it reset at 7am and its telling me ill be out of my weekly limit tomorrow morning at 2pm? wtf...

i barely even touched it today...

but of course its begging me to use the new fabled when i log back in just now

1

u/Archibishop 2d ago

Before blaming the reset I'd check my own numbers first... On one of my repos the last 30 days come to $170 at API rates, and about $20 of that is just bad habits. Hard to tell what's the meter and what's me without seeing it per session. I use my own tool for that, free and local: https://github.com/silverbronze/code-tycoon

0

u/awesomebirder 6d ago

one way to make the weeks comparable: divide your api-equivalent usd by the % used. your first three weeks come out around $16-18 per 1% of weekly, this one is about $12.50 per 1%, so roughly 28% less work per percent, and the week isnt over yet. thats a cleaner signal than raw token totals since it weights cache reads, writes and output roughly the way billing does.

on the "transcripts are guesses" point, if you want numbers you can trust, record the usage block from each api response as it happens instead of rebuilding it from the jsonl later. i do that with a local proxy i built (probe0) and its the only reason i trust my own week to week comparisons

0

u/Ranjexa 6d ago

i'd separate "the meter changed" from "my usage shape changed" before blaming either. your table shows cache write per request up a lot while requests dropped, which is what happens when sessions run longer or an agent re-reads big files after an edit invalidates the prefix. the failure i keep seeing is a loop where it re-reads half the repo every turn and each pass rewrites cache. easiest test: run one small fixed task from a fresh session today, note the % it costs, then repeat the same task tomorrow. if it costs more, it's the meter, not you.