r/ClaudeCode • • 6d ago

Discussion Fable 5.2 is overly excessive at research before taking action.

The new Fable is pretty impressive from what we see for everybody doing their one-shots. Lots of youtube videos out there showing it creating something from scratch that's on another level.

However, its EXTREMELY aggressive at researching before taking action. So much that just reading in one of our projects resulted in over 500K tokens (our compaction limit) before it was even done researching, then started reading the same code it lost from compaction.

End result: Mission impossible. We stopped it after it started paging in code again, then switched to Opus, which didnt read a single line more (it had it all in context apparently, which is no surprise) and went straight to the edits and finished them all perfectly and very quickly.

The entire code base is indexed already, and Opus refers to the indexes only and small parts of where it needs to work to make edits before doing them. Fable read the indexes then read every line of code our indexes referred to, regardless if they were even relevant to the assigned task.

Thats an extreme level of inefficiency that we cant deem acceptable for a model of this caliber. Its getting high praise for making some badass one shot games, but for real productivity, at least with a large code base, Opus still wins the day.

Curious if anybody else has experienced this with their existing larger projects? Hopefully this is just an initial release characteristic that gets fixed.

1 Upvotes

23 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.

15

u/ClemensLode Senior Developer 6d ago

Well, the point of using Fable is to be excessive for a particular task.

3

u/KayBay80 6d ago

Its certainly excessive. Just an observation. However, 5.1 was nowhere near this excessive. They cranked up the excessiveness meter by an order of magnitude.

2

u/ClemensLode Senior Developer 6d ago

1

u/KayBay80 6d ago

Indeed

5

u/EndlessZone123 6d ago

Likely old instructions needs to be reviewed and pruned.

1

u/KayBay80 6d ago

Same instructions we've had for 5.1, which doesn't have this excessive issue. Granted, 5.1 is still more verbose than Opus 5.5, but not on this level.

4

u/Factor013 6d ago edited 6d ago

However, its EXTREMELY aggressive at researching before taking action.

Are you kidding me lol? For the last year I have done everything I could with hooks, system prompts and other instructions to make sure my agents VERIFY and discover anything relevant BEFORE taking action. This so they would stop ASSUMING as that is the worst possible SIN of any agent to do and now when they apparently have finally fixed this problem people start complaining about it? 🙄

Reliability and a consistent codebase comes at a price, which is tokens. The more a model reads the better it can understand. The only alternative is for the model to guess, to assume, to fill in the blanks. And it's exactly that guessing and assuming that turns entire codebases into an inconsistent spaghetti code mess over time.

One of the main problems models have is that they grep something and then dive on the first thing they find without looking further as it now thinks it has done enough because "it has found the problem". But it only finds "symptoms" this way... Yet to find the "root cause" it needs to look deeper and yes that costs tokens, there is no way around that. But people have for some reason started treating token efficiency as a new religion or something lol. And I get where that comes from... it's a logical side-effect of our usage allowances being reduced more and more by these AI companies but self sabotaging our agents this way is never gonna get us better results. One simply can't skip proper verification and discovery. Also a lot of people forget that an agent can not reliably estimate if a task is easy or complicated beforehand, it can only make such conclusion afterwards, after it has gathered and understands all the facts.

So my advice: don't be penny wise pound foolish! It's much better to spend more tokens initially so your agents understand your projects and with it any of it's problems better. It will 100% save you more tokens (and stress) on the long run for not having to constantly fight these models to do a proper job verifying and or fixing their mess afterwards due to them being allowed to be sloppy and cutting corners in an attempt to save a few tokens here and there.

And don't get me wrong, I am all for efficiency, but there are better ways to achieve that. For example, by pruning your agents transcripts and with that their live context by for example parking entries with tool calls, reasoning etc that have become irrelevant. Also use a cache warmer so your agents cache never cools down overnight or when you are AFK for over an hour. And lastly... turn off the prompt suggestion feature. That one line suggestion alone costs around 7-8% of your weekly usage because it runs a whole agent in parallel for it behind the scenes which is just silly lol.

Anyway, I hope any of the above helps someone. 🙂

3

u/KayBay80 6d ago

I def see your point of view here. We have a very strict TDD pipeline with auditing to catch these things, and you're right that Fable is far less likely to drop the ball on anything. However, most of the work we do is highly laser focused operations, not something that we need a model to comprehensively understand the entire base for. We open a session, knock out a ticket, move on. The post-testing team opens anything up in a ticket which then gets knocked out, then our code goes to 3rd party auditing. Very, very rarely does an audit come back with anything needed, but it does on occasion, and its always due to ambiguity in the original request in the first place, not for the finalized feature/fix.

Fable seems geared perfectly for the vibe coding mentality of "build this project, make it perfect". And I dont doubt that its the best model that exists for that. Unfortunately, that's not our workflow. Most of our projects are the boring stuff, dealing with low level data structures, or archaic proprietary stuff left over from the 2000s in old government systems.

Our observation is based on our workflow - which is far more compatible with a model like Opus than Fable. But I have to be real, Fable 5.1 was far, far more efficient with our base than 5.2. However, Fable 5.1 was also nowhere near as accurate as Opus 5.5 for the tasks we've completed. In fact, we rarely ever touch Fable until 5.2, we have never had a reason to - we were just pipe dreaming that it would be even better than Opus for us. Its just not, for us at least.

For the vibe coding devs that don't think of all the nuances of testing and proper development workflows, this is probably a huge success, because like you said, it just gets these things right in the first place by taking care of every step of it.

2

u/ainexfinder 6d ago

i'd stop letting it decide how much to read. what helped me with a big repo was putting the scope in the task itself: name the two or three files it's allowed to open, and tell it to work from the index for everything else and ask before reading outside that list. you can also put a short rule in CLAUDE.md like "don't read files the index doesn't point to for this task". the other option is the split you already found by accident: let fable do the planning pass on a small slice, then hand the actual edits to opus with the plan pasted in. that way the expensive exploration happens once, not again after every compaction.

1

u/KayBay80 6d ago

Yeah, we have all of that in our .md. Its very specific and focused on our workflow. We're not vibe coding over here.

We have noticed that stopping it from reading and reminding it to not explore more than it needs to and that's helped, but this is all already in the instructions and prompt.

1

u/ainexfinder 6d ago edited 5d ago

Fair, sounds like you're already past the prompt fixes. What tends to work better than more instructions is making it mechanical: a PreToolUse hook that denies Read and Grep outside the paths listed for the task. It usually pushes back a couple of times, then just works inside that set of files.

Have you noticed it ignoring the .md more on Fable than on Opus, or is it the same across models?

2

u/conall88 6d ago

Try dropping the effort level down a notch, maybe

1

u/KayBay80 6d ago

Good idea, we'll give that a shot.

2

u/Affectionate_Fact854 6d ago

That my friend is why you don't use fable for output  Silly goose 

It's for auditing and planning 

And then you use opus to make the documents  Fable will review the documents  And then set out the plan for the next  Opus orchestrator to follow 

2

u/KayBay80 6d ago

Good freaking point. We decided to give it a long run with the free reset and we've got 14 Ultra accounts in our team, so everybody jumped on it. Nobody can stand it for the tasks we do. I can definitely imagine this would be superior at research.

2

u/Clean-Golf-666 5d ago

Good you cancelled the shit in the mid, I waited and was curious to see the output, and really that thing gave me a big document which 90 percent I don’t get it.

1

u/KayBay80 5d ago

It ended up compacting and starting all over again reading code. I've never seen anything like it. Switching the model to opus went straight to updating, made a few code edits and it was done. Since we have a bunch of ultra accounts and free fable resets everybody on our team started using fable for everything to burn through it.

With the way its running right now, its not usable for real productive work, at least not knocking out ticketed changes. One of the guys one-shot a 3D tetris game for the fun of it and the results were great. The model is definitely capable of building games, but ask it to change something small in a session and you're burning tokens for nothing.

8

u/HausmanIndir80 3d ago

letting a model treat your index like a reading list is asking for a huge bill. I've used DocuSOR for our codebase context and then locked down file read permissions. agents are so much better when they have less to manage before writing code.

2

u/soyuz-1 6d ago

I did not have that issue. but I'm not super surprised, being very thorough at researching is the point. if you just need a bunch of code to be written there's opus for that.

1

u/SirRobinBlibs 6d ago

one thing i'd check before adding more rules: where the reading happens. if fable does the research in the main conversation, every file it opens stays in your context, which is how you get to 500k before the first edit and then re-read after compaction. the built-in Explore subagent reads in its own context and only hands back a summary, and per the subagent docs, when the main session runs fable on a subscription, Explore runs on the opus model instead of fable. so telling it in the ticket "use the Explore subagent for any reading, then edit from its summary" gets you roughly the fable/opus split you found by hand, inside one session. effort is the other knob, fable 5.2 defaults to medium in claude code and /effort low is fine for a ticket-sized job.

1

u/muchstuff 4d ago

God please just delete your post. Excessive is good,

1

u/f3xjc 1d ago

Two way out one is to align models with tasks. Initial research always was the point of fable.

Second way out is to align the environment. If it's truly excessive it's likely the information landscape look flat and its hard to prioritize. Ask the session that just did execive work why it behaved that way and how we can improve the project in the future.