Loading video...
Video Failed to Load
Fable 5.2 vs Opus 5.5 Vibe coding is coming for engineering 😨
67,945 views • 3 days ago •via X (Twitter)
32 Comments

coming for engineering, but first it's coming for my usage limit 😂

Fable 5.2 physical product design capabilities is impressive so far.

finally we will see innovation in toilet design again

You can definitely see the improvement.

the gearbox has been vibed!!it feels more textured now Needs to start fixing them too.. I’ve spent so many tokens on mechanics

Hardware engineering has been demystified

Just remarkable

这么强

I mean, if I could have unlimited fable I would do that too 😅 What surprises me is that the jump between Fable and Opus it's not that different, considering opus is way more efficient than Fable

Still not there yet but getting closer by the day. I also used Fable 5.2 to build this AI-generated CAD that checks every requirement on the real geometry before handing you the part

我去

Super interesting approach, how are you handling edge cases when scaling concurrent workloads?

It's giving "AI-generated steampunk".

That's some real progress!

Two gears spinning at 6.00 RPM side by side is the frame I would screenshot before arguing either way.

Now the question is what will happen next, after Opus 5.5?

which one would you actually trust on a codebase you care about though? looking good in a demo is one thing

It has already arrived

the output generated by the claude fable 5.2 looks insane, realistic and premium.

The shift in how we approach engineering is actually happening right now:

From an engineering perspective, this is neither hard nor is it impressive. I think the last generation of models could do this.

Not really because this is not an actual CAD based engineering drawing.

Wow the AI knows how to build something invented 200 years ago 🤯🤯🤯

Hey @grok Visuals for bike motor 10 strokes with modern engineering concepts to build design!

Same prompt and harness for both? On a one-shot boat ride game, Fable 5.2 wrote about twice the output tokens of Opus 5.5 for me (128k vs 59k).

Is this just a carefully staged demo, or is this how it actually looks? I ran a quick test myself, and the difference in display quality wasn't nearly that big.

do you really think so? what would be its use case in that sector?

hypoid gear set generation would be interesting. This is an iterative design which starts with target parameters such as n of teeth, pressure angle, offset etc. Generate CAM and then even regular CNC may cut hypoids efficiently without need of specialized machinery.

it's coming for the drafting. someone still has to decide what the part must survive, and sign the drawing

Didn’t it already? Software down rest to go

Same comparison trap. Both demos look flawless, then the real codebase shows up with 40 tabs open. A common fix is to test both on one small real task, not the demo. Heads up, watch the output token cost before picking a winner.

Opus 5.5 和 Fable 5.2 在 vibe coding 场景下差距大吗?

