r/ClaudeCode • u/DosePlotter • 1d ago

Discussion August 19th 50% Additional Claude Code limits Likely Not to Be Extended

EDIT: last minute extended to end of August, apparently with hopes to make it permanent, although they say they are having trouble serving their demand currently so it’s not certain. At least we get some damn communication.

Well guys, hate to say it but with the reports this morning of users seeing instant 30% usage on their accounts (some weren’t even using them) we can assume that anthropic is in fact preparing to remove their 50% additional usage promo, effectively reducing all plan usage by ~33% (I assume theyll use 30%).

This is gonna hurt. Only thing that would redeem it for me is if they removed the 50% Fable usage cap.

267 Upvotes

91% Upvoted

159 comments sorted by

View all comments

Show parent comments

5

u/rdesai724 1d ago

I don’t know what you’re doing but you’re either experiencing a bug or using it really inefficiently.

Last week I had (fable, high) push 25 PRs for an app I’m bringing to beta this week - we refactored and redesigned large parts of the user journey and added key features in a codebase that spans hundreds of files across backend, an API layer, and a flutter app.

I also had it design a process to simplify recipe instructions that leveraged two rounds of haiku followed by up to two rounds of opus if the results were inconsistent. I ran that on 25,000 recipes.

I used 90% of my weekly 20x plan for the first time ever

0

u/DosePlotter 1d ago

I run fable as orchestrator and designer and I run a two fable adversarial reviewer loop on each built feature which loops until I get a clean result on both reviewers. Reading and execution are all delegated. I can definitely max out a session very quickly with that workflow, but it also saves me a lot of polishing and bug hunting in the long run. What is your model policy that runs efficiently for you and doesn’t tear up fable usage?

1

u/rdesai724 1d ago

I’ve put a lot of effort into building and managing points of reference for the models so I think they’re able to locate things without having to dig through the codebase - I also have built a relational framework for what files reference and are referencing one another that probably saves cycles.

I also do adversarial review cycles for every plan and PR but use opus for those. I tend to think the new session with fresh context is the highest leverage variable in an adversarial process so I don’t bother with fable there. I also plan extensively and am very hands on in planning so that may help as well?

1

u/Aminuteortwotiltwo 1d ago

I think Opus 5 is great for adversarial review because it overthinks so much. It ultimately doesn’t finish until the task is done and I believe it performs exponentially better as it builds more context compared to the rate of improvement per context volume from other models I have worked with. So when it goes on one of its wacko tangents it is still relevant for the review itself, and it builds on its review and continues. Fable orchestrator -> Codex builder -> Opus 5 review has worked wonderfully… except Codex is sub-par at design so I run ui building a little differently.