I left Claude for months. Opus 5.5 is why I'm back

Playback speed

Share post at current time

Share from 0:00

0:00

Generate transcript

A transcript unlocks clips, previews, and editing.

I left Claude for months. Opus 5.5 is why I'm back

🎙️ I abandoned Claude for months because it drove me insane. Opus 5.5 changed that, and I'll show you exactly where it's earning a spot back in my stack for frontend, SVGs, and agentic tasks

Claire Vo

Sep 22, 2026

Listen or watch on YouTube, Spotify, or Apple Podcasts

I’ve been off Claude for months. Not because it got dumb, but because it got annoying. The rambling, the hedging, the preachy little disclaimers on tasks that didn’t need them. I moved most of my daily work to Codex and I didn’t miss it. Then Anthropic shipped Opus 5.5: 40% cheaper than Opus 5, faster, and with what they’re calling a fundamentally different alignment approach. I ran it for a week across real work, including four long-running agentic tasks, a full ChatPRD homepage redesign, an SVG benchmark, and one very firm refusal, and I’m ready to give you the honest verdict. There’s a lot to like. There are still two things that drive me a little crazy. And there’s one capability I genuinely wasn’t expecting.

What you’ll learn:

Why I walked away from Claude entirely, and what it took for me to come back
The real cost math on Opus 5.5 and why pricing matters more for agentic work than single prompts
What happened when I ran four long-running agentic tasks, including one that tried to manipulate Claude mid-run
Why Opus 5.5 is now my go-to for frontend prototyping, and where it still lets me down
The one capability I genuinely didn’t see coming, and no other model in my stack can match it
The moment Opus 5.5 told me flat-out no, and what that says about where Anthropic’s safety posture actually lands in practice
Where Codex still wins, and how I’m splitting my model stack after a full week of testing