Why I prefer Opus 5 to Fable 5

Posted by novlrdotcom 6 hours ago

Counter17Comment7OpenOriginal

I've been experimenting with both since the moment each came out. 4 games, 3 websites and 2 content creation engines later - I think I'm ready to share a bit of my experience and opinion.

WHAT I'VE NOTICED ABOUT FABLE

1. Gold in, gold out - meaning I've had the best results by making all my design decisions before giving Fable the kickoff information and prompt. It's much more comfortable making decisions by itself - decisions it won't tell you about - unless you explicitly tell it what it can and can't decide for itself up front.

2. It's a black box - which is an extention of the point above in a way. I've used the analogy of an agency when I've described it to people, i.e. it'll take a brief (what Fable itself describes as "an order") and go off and run with it, only coming back once it's done. I once had a Fable conversation work independently for 9 hours buidling out a client self-service portal for me. All I had to do was type 'Continue' once it hit its session limits every 5 hours.

3. It's insanely powerful - so if you've got everything worked out up front by thinking and working through it with an Opus conversation, you can get the most staggering results. It creates its own sub-agents, does its own testing and self-verification, and ships you back a finished product. It blew my mind.

BUT I PREFER OPUS 5

Why? Because it's not a black box.

1. It reports back - it seems to pause at natural phase gates and give an update on what it produced and why. There's a rhythm to it that keeps you the user involved.

2. It's just as capable of spinning up sub-agents and doing its own testing and verification.

3. It genuinely is a lot cheaper - for example when Fable runs on a task my Claude Max limits burn out in roughly 30 to 45 minutes (Fable is FAST). But then that leaves me twiddling my thumbs. Opus 5 feels more methodical somehow (which might just be because it comes back to the user, resulting in a slower cadence). Or maybe the better way of putting it is that Opus keeps you the developer involved throughout. And it feels like it's more interested in giving you exactly what you want. Fable doesn't do that - it basically just takes the brief and does its own thing.

I simply wanted to share my experience as I've quickly reached the point of familiarity and thought that might be valuable to others who are experimenting with these frontier models.

Look forward to your thoughts. Cheers.

Comments

Comment by ocd 2 hours ago

I probably haven't adjusted things well enough to make the most of Opus 5, but yes, I did provide a lot of information in advance with Fable 5 probably mostly because I was concerned about resource constraints. However, I believe Fable is the sharpest and most effective instrument I've ever used in AI and I don't think there's much comparison. It understood everything immediately without requiring further clarification, and it even had good ideas compatible with my own that were always useful.

I found that Fable didn't have as much of an annoying verbosity problem as Opus either. Anything it did say was genuinely relevant and without filler.

Comment by oggreen 3 hours ago

I use Sonnet 80% of the time when I'm on claude.ai and on Claude Code my main agent is Opus and typically my sub-agents are Sonnet.

I use this setup mainly because I genuinely don't know if anything I'm doing is complex enough to need Fable and I don't want to run up my usage too much. It's basically like trying to kill a gnat with a sledgehammer. Hell, at work Haiku almost always works just as well as Sonnet does and its much cheaper/faster. It does seem to struggle with complex structured outputs however.

The only time I've really used it (and I've been genuinely impressed) is when I'm trying to get structure for something that's abstract.

So I wouldn't say I prefer any of them, just that I try to match them with how complex my use case is.

Comment by adrianco 3 hours ago

Without discussing the task itself, this isn’t useful. Coding small problems in Python works on low effort with older models. Less common languages on harder problems needs more… I’ve been running coding experiments, see https://github.com/adrianco/retort

Comment by hardrave 2 hours ago

I had almost the opposite experience. Fable managed to build a pretty advanced low-level systems project for me end to end, while Opus kept getting stuck on the overall architecture. Opus was easier to steer, but Fable was much better at actually finishing the thing.

Comment by spottedmarley 5 hours ago

I'm right there with you, in theory. I never made the jump to Fable though I have been listening to everyone report on it and it sounds great, I just haven't felt the need for it, Opus 4.8 is plenty for what I do. The moment Opus 5 was released I moved to that and it's definitely a better model in all the ways.

Comment by KinetiNode 28 minutes ago

i use free tier TᴖT

Comment by uncivilized 2 hours ago

Dear diary

Comment by SangLee 2 hours ago

[dead]