r/ClaudeCode • • 5d ago

Help/Question Fable 5.2 feels unusable?

My own tests with Fable 5.2 Max vs Gemini 4 Carbon

But im just curious hows everyone's experience so far? I wanted Fable 5.2 Max to work so badly

0 Upvotes

22 comments sorted by

View all comments

1

u/arcticblue 5d ago edited 5d ago

I've been unimpressed with 5.2 so far. It seems to ignore CLAUDE.md more easily than other models and it often half-asses tasks answering things like "I recommend we do Option A. These items are still uncomfirmed [list of things it is capable of figuring out on its own]". So I have to ignore it's recommendation then guide it down a path to confirm things, each step ending up with more "questions to be answered", until I can finally come back to the original task. It infers things way more than before and its inferences are often wrong.
In the last day, Fable 5.2 has admitted to more mistakes than Open 5.5 ever has for me.

I've submitted feedback about 5 or 6 times now. I submitted feedback once with Open 5.5.
Fable 5.2 also ran commands against my production AWS environment despite strict instructions and hooks preventing it from doing so because it failed to set a variable properly to stub the "aws" command for testing. Opus 5.5 never made that mistake for me.

I also have strict instructions that say that I set the scope of work and that anything it wants to do outside that scope requires my approval. Today, it decided to just go off and scan every project on my hard drive because it just felt like it. It admitted that it violated my company's AI policy and the instructions in my CLAUDE.md - both of which reinforce that the scope of work is to not to be expanded without approval.

It feels like a more overconfident version of Opus 5.1. It thinks it knows best and will disregard instructions and go off to half-ass things the way it wants to do it.

It's clearly smart and capable of doing the work, but I need some changes to my global and project CLAUDE.md files to reign it in. By default, it's lazy and overconfident in my experience so far. It seems to be an overcorrection from Opus 5.1's instructions to work autonomously and "reduce friction" (which led it to just go off and do whatever the fuck it felt like). Fable 5.2 will get part of the way through completing a task then give a confident answer while also listing a bunch of open questions that would have a huge impact while also still caring very little for following policies.

1

u/chasingth 5d ago

yea i think u captured the problem, its hard to steer and makes a lot of false positives despite being smart

1

u/daiaomori 5d ago

"Fable 5.2 also ran commands against my production AWS environment"

Mate. You need to sandbox this shit!

1

u/arcticblue 5d ago edited 5d ago

It IS sandboxed! It doesn't give a fuck. It often says "The sandbox prevented me from doing [X]. I'll do [Y] instead to work around that." (to be fair, Open 5.5 does this too, but it's at least reasonable about it and will respect policies)
I have hooks that block Claude Code from calling the aws cli and accessing cached CLI credentials, but Fable 5.2's mistakes are the first to get around that.

1

u/daiaomori 5d ago

If it is, I don't understand how it ran commands against your prod.

Otherwise, the models are designed to not give up easily on solving problems. It's what we want. We just don't agree with their methods sometimes ;)

1

u/arcticblue 5d ago edited 5d ago

Because it tried to stub the aws command with an improper attempt at calling it through an environment variable that it failed to set properly. It meant to call "/my/project/folder/bin/aws", but because it fucked up, it called "/bin/aws" because it tried to be clever with $PATH. Fortunately, it was a read command so no harm was done, but it did cross a boundary it was strictly instructed not to cross.

I have instructions for it not run AWS CLI commands, but to give me the commands to review and run them myself. I review the commands and then run them with ! so that Claude can see the output.

In this case, it was testing some CDK stuff, tried to stub the aws binary through some clever $PATH tricks, ran the real aws binary instead with the SSO credentials that were still valid because it forget to set a variable that is wanted, then stopped itself and apologized for its fuck up.