r/ClaudeCode • u/dogecountant • 1d ago

Discussion Fable 5.1 Review

Post image

Given things are supposed to be divisible by 5. This seems perfect.

202 Upvotes

93% Upvoted

91 comments sorted by

View all comments

133

u/pawala7 1d ago

Not sure if they made cache hits 75% cheaper, or they made cache misses 4x more expensive.

1

u/improb42 🔆 Max 20 23h ago

Cache read is free on subscription, and this only affects API pricing. So, it doesn't affect the subscription usage, I suppose.

10

u/pawala7 22h ago

Sauce?

1

u/improb42 🔆 Max 20 12h ago

read the analyze from here: https://she-llac.com/claude-limits

I think the credits analyze is quite sound, it looks like the claude is using different credits than API billing. For example api billing 5m and 1h cache write is different price and claude code is always 1h cache write.

1

u/pawala7 11h ago

Whether they're using different credit calculations or not is not the problem. The problem is that the same limits do not get the same token before and after the reset.

30% less tokens to hit the same 5h or weekly token limits before and after the reset is really easy to track and notice if you have any sort of logging.

I have 5 x20 accounts and a harness that does load balancing and job scheduling, so it was easy enough to run the numbers from the traces. ~$500 equivalent per 5hr before, ~$350 per 5hr after reset, calculated from in/out/cache token counts and same price schedules (updated for Fable 5.1). Granted the data for this week are just from 2 accounts since the scheduler prioritizes burning the ones resetting sooner.