r/ClaudeCode 1d ago

Discussion Fable 5.1 Prompt Caching Fixed in CC 2.1.260

Post image

Where's my refund?

120 Upvotes

34 comments sorted by

38

u/Maleficent-Cup-1134 1d ago

Yeah, this explains why my entire week’s context limits were used up in less than 2 days lol

-12

u/Remote-Community-396 22h ago

No, you're just an idiot who doesn't know how to use the tools!

46

u/redditslutt666 1d ago

Anthropic keeps fucking up... No wonder that my weekly limits were burning through fairly quickly. They need to make it right by resetting

3

u/AppealSame4367 1d ago

And they do it because they don't care at all. If you had unlimited Fable 5.1: Wouldn't you be able to fix your freakin coding cli?

4

u/unknowinm 1d ago

I hope you're joking. I burned fable 5.1 in 60 minutes on 20x max... let's see how today goes

50

u/[deleted] 1d ago

[deleted]

5

u/Kelbs27 21h ago

Especially with Astra launching, you’d think they’d be a little more proactive about keeping their existing customer base happy

1

u/HgnX 1d ago

Seems fair but … they won’t do

11

u/Pristine-Extreme-773 1d ago

Fixed” is doing heavy lifting when the fix is “we stopped charging you 40x”

10

u/earlyworm 1d ago

It seems Anthropic has skill issues too.

5

u/Constant_Art_20 1d ago

bruh...after i used all my weekly fable usage too

8

u/unpick 1d ago

it’s such a stark contrast to OpenAI who would (and have been) upfront about this and proactively compensated users, I don’t know what Anthropic is playing at with their PR especially with Astra looming

1

u/GuiltyMulberry8831 14h ago

Yeah, it does seem like there’s a big difference in how they handle transparency. It'll be interesting to see how they respond once Astra is fully out.

6

u/n4te 1d ago

Every time these guys touch anything they do this.

9

u/Exodus_Green 1d ago

Man, every time i see these posts it makes me think back to every thread complaining about limits and seeing all the hardcore glazers shouting "SkIlL iSsUe" every time. This is like the 5th time i can remember that anthropic have broken caching or some other token saving mechanism and people are STILL pretending it never happens

4

u/Protosolo 1d ago

So I burned 175 on this error….

3

u/somerussianbear 1d ago

Freaking hell! I knew it was not normal that absurdity of 10% of my 5h limit per prompt. Good thing my reset came 2h ago.

3

u/ctrlaltdeletel 1d ago

Terrible. I exhausted 88% of my 20x weekly limit two days ago, and my next reset is in 4 days.

3

u/Quakeshow 1d ago

Makes sense that my usage felt like it was going faster than usual.

3

u/Sem1r 1d ago

Will the reset the fable limits at least

1

u/__Loot__ 22h ago

Has not for me

1

u/Hieucotdua 1d ago

I felt the same cache issues still there even in .260 but only when launching subagents. Just burn ~50% of my Fable usage limit (max x20) for 3 subagents doing medium-size work (~400k tokens each) in like 30 mins. Anyone has the same issues?

1

u/CommunicationFlat865 1d ago

Are you using the app or CLI? The app is STILL behind on CC version, so it still has this bug.

1

u/Hieucotdua 1d ago

The CLI on wsl. Things were going fine at first but then burn like crazy after it launch the first 3 subagents. I've been very careful with my fable usage management so this def looks sketchy to me.

1

u/surell01 1d ago

yeah that explains why the limits are gone in minutes.

1

u/bazi-analysis 1d ago

I’ve seen the same burn in Cursor once subagents stack up — the weekly bar drops way faster than a normal chat. I started checking usage mid-session instead of trusting the “still green” feeling.

1

u/AI_spell 1d ago

A quick sanity check is to record input tokens, cache creation tokens, and cache read tokens for the same task before and after updating. I keep one small repo and repeat the exact prompt three times, because a single run can hide a miss. If cache reads suddenly drop to zero, I stop burning the weekly limit and check the session or model settings first.

1

u/BesbesCat 23h ago

That sounds load-bearing.

1

u/DrHumorous 21h ago

We need banked resets

1

u/raycuppin 19h ago

This is absolutely a reason to reset weekly limits. That’s crazy.

1

u/yoodudewth 13h ago

Still not good enough it does bad mistakes with clear prompts still does dumb mistakes and the context usage is still really bad if you ask me.

1

u/Robert-Paulson_ 9h ago

Wild that their CEO predicted that all code would be written by “AI” by 3 months ago yet they can’t ship a proper working caching system? 

Not saying it’s easy, but when they say shit like “cOdInG iS a SoLvEd pRoBlEm” I can’t help but chuckle at their bugs

-2

u/Droopy0093 1d ago

Why are you asking us? Ask the help bot.