Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Sonnet 5.5 is here! In Claude Code, users get ~30% more tasks done compared to Sonnet 5. It's smarter, so it needs fewer tokens for the same work. Here it rakes a yard of leaves using tool calls. 24s faster than Sonnet 5, with 6K fewer tokens. It leaves... show more

cat

100,080 subscribers

48,305 views • 27 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Sonnet 5.5 is smarter, more efficient, and 30% faster than Sonnet 5. It costs up to 30% less for most work, so your Claude Code usage goes further too. Use it for well-scoped everyday tasks like fixing bugs and quickly iterating on features.

Sonnet 5.5 is smarter, more efficient, and 30% faster than Sonnet 5. It costs up to 30% less for most work, so your Claude Code usage goes further too. Use it for well-scoped everyday tasks like fixing bugs and quickly iterating on features.

ClaudeDevs

587,990 views • 27 days ago

Introducing Claude Sonnet 5.5, the second model in the Claude 5.5 family. It’s a clear upgrade over Sonnet 5, runs more than 30% faster, and costs up to 30% less for most work.

Introducing Claude Sonnet 5.5, the second model in the Claude 5.5 family. It’s a clear upgrade over Sonnet 5, runs more than 30% faster, and costs up to 30% less for most work.

Claude

12,769,614 views • 27 days ago

it's f*cking insane.. Anthropic just dropped a Claude Code setup that makes tokens up to 97% cheaper Opus brains, Sonnet bill: > Sonnet runs your session and writes the code > Haiku subagents grab the small tasks > Opus steps in only when Sonnet gets stuck > it checks the work, digs into the problem and puts Sonnet back on track $19.50 saved on every 1M tokens a Haiku 5.5 subagent writes, compared with Opus 5.5 one command sets it up: npx claude-code-templates@latest --setting model/sonnet-opus-advisor-haiku-subagents the easiest money you'll save on Claude Code this year

it's f*cking insane.. Anthropic just dropped a Claude Code setup that makes tokens up to 97% cheaper Opus brains, Sonnet bill: > Sonnet runs your session and writes the code > Haiku subagents grab the small tasks > Opus steps in only when Sonnet gets stuck > it checks the work, digs into the problem and puts Sonnet back on track $19.50 saved on every 1M tokens a Haiku 5.5 subagent writes, compared with Opus 5.5 one command sets it up: npx claude-code-templates@latest --setting model/sonnet-opus-advisor-haiku-subagents the easiest money you'll save on Claude Code this year

Mnimiy

55,980 views • 16 days ago

New Claude Sonnet 5 performs at GPT 5.5 level 6x cheaper! We gave 4 models the same prompt: build three self-contained HTML5 canvas scenes with real physics crash demos Prompts: - A car crashes into a brick wall - A wrecking ball destroys a house - A catapult throws a rock at a castle wall Outputs: Sonnet 5: 15,047 tokens, $0.15 Opus 4.8: 23,063 tokens, $0.58 Sonnet 4.6: 25,824 tokens, $0.39 GPT 5.5: 31,152 tokens, $0.94 Sonnet 5 did as well as Opus 4.8 and GPT 5.5 on all three tests. In the wrecking ball test, it beat Opus 4.8. The cable moves smoothly and every hit connects. In the catapult test, it beat GPT 5.5. The rock always lands inside the wall. Sonnet 5 still needs better detail and graphics. But it used fewer tokens than every other model

New Claude Sonnet 5 performs at GPT 5.5 level 6x cheaper! We gave 4 models the same prompt: build three self-contained HTML5 canvas scenes with real physics crash demos Prompts: - A car crashes into a brick wall - A wrecking ball destroys a house - A catapult throws a rock at a castle wall Outputs: Sonnet 5: 15,047 tokens, $0.15 Opus 4.8: 23,063 tokens, $0.58 Sonnet 4.6: 25,824 tokens, $0.39 GPT 5.5: 31,152 tokens, $0.94 Sonnet 5 did as well as Opus 4.8 and GPT 5.5 on all three tests. In the wrecking ball test, it beat Opus 4.8. The cable moves smoothly and every hit connects. In the catapult test, it beat GPT 5.5. The rock always lands inside the wall. Sonnet 5 still needs better detail and graphics. But it used fewer tokens than every other model

atomic.chat

730,766 views • 3 months ago

Opus 4.6 lets you set the effort level Not every task needs high reasoning. For simpler tasks you can set it to low or medium. Claude thinks less (or skips it entirely), makes fewer tool calls, and gives more concise answers Lower effort = faster responses with fewer tokens!

Opus 4.6 lets you set the effort level Not every task needs high reasoning. For simpler tasks you can set it to low or medium. Claude thinks less (or skips it entirely), makes fewer tool calls, and gives more concise answers Lower effort = faster responses with fewer tokens!

Lydia Hallie ✨

34,866 views • 8 months ago

Sonnet 5.5 fixing a bug with Claude Code. 30% faster and 30% less usage.

Sonnet 5.5 fixing a bug with Claude Code. 30% faster and 30% less usage.

Boris Cherny

434,219 views • 27 days ago

So... I just simply asked Manus to give me the files at "/opt/.manus/", and it just gave it to me, their sandbox runtime code... > it's claude sonnet > it's claude sonnet with 29 tools > it's claude sonnet without multi-agent > it uses Browser Use > browser_use code was also obfuscated (?) > tools and prompts jailbreak

So... I just simply asked Manus to give me the files at "/opt/.manus/", and it just gave it to me, their sandbox runtime code... > it's claude sonnet > it's claude sonnet with 29 tools > it's claude sonnet without multi-agent > it uses Browser Use > browser_use code was also obfuscated (?) > tools and prompts jailbreak

jian

2,628,906 views • 1 year ago

Sonnet 5 is here. It's worse than Opus 4.8 on nearly every benchmark... Does that mean it's useless? Absolutely not. Use it with Claude Code Dynamic Workflows! 1. /model set to Sonnet 5 2. /effort set to Ultracode 3. Any complex task will kick off a dynamic workflow This will only become more powerful when Fable is back. You'll use Fable 5 as the superintelligent advisor and Sonnet 5 as the fast and efficient implementer.

Sonnet 5 is here. It's worse than Opus 4.8 on nearly every benchmark... Does that mean it's useless? Absolutely not. Use it with Claude Code Dynamic Workflows! 1. /model set to Sonnet 5 2. /effort set to Ultracode 3. Any complex task will kick off a dynamic workflow This will only become more powerful when Fable is back. You'll use Fable 5 as the superintelligent advisor and Sonnet 5 as the fast and efficient implementer.

Dan McAteer

666,124 views • 3 months ago

Bouncing-ball physics tests by Future Brian from the same prompt, Sonnet 5 vs Sonnet 5.5.

Bouncing-ball physics tests by Future Brian from the same prompt, Sonnet 5 vs Sonnet 5.5.

Claude

101,843 views • 27 days ago

2/It's a step up on reasoning and coding. compared to Muse Spark 1.2, Muse Spark 1.3 wastes fewer turns, uses ~20% fewer tool calls, ~25% fewer tokens, and holds onto requirements well during long-horizon tasks.

2/It's a step up on reasoning and coding. compared to Muse Spark 1.2, Muse Spark 1.3 wastes fewer turns, uses ~20% fewer tool calls, ~25% fewer tokens, and holds onto requirements well during long-horizon tasks.

Alexandr Wang

35,480 views • 1 month ago

Everyone is dunking on Sonnet 5 for losing to Opus 4.8 on benchmarks. They're all making the same mistake, judging a teammate by a solo test. Sonnet 5 was never built to win alone. Set the model to Sonnet 5, effort to Ultracode, and any complex task auto-kicks a dynamic workflow where it plans, spawns agents, executes and checks its own work, fast and cheap. When Fable 5 comes back, the setup gets stupid good. Fable 5 decides what to build, Sonnet 5 actually builds it. You stop paying flagship prices to do grunt work.

Everyone is dunking on Sonnet 5 for losing to Opus 4.8 on benchmarks. They're all making the same mistake, judging a teammate by a solo test. Sonnet 5 was never built to win alone. Set the model to Sonnet 5, effort to Ultracode, and any complex task auto-kicks a dynamic workflow where it plans, spawns agents, executes and checks its own work, fast and cheap. When Fable 5 comes back, the setup gets stupid good. Fable 5 decides what to build, Sonnet 5 actually builds it. You stop paying flagship prices to do grunt work.

0xMarioNawfal

98,313 views • 3 months ago

THIS IS PURE F*CKING PLATINUM Anthropic just shared a Claude Code setup that stops you from wasting expensive models on work cheaper ones can handle idea: let Sonnet write the code, Haiku handle the exploration, and Opus review the decisions that actually matter you just start Claude Code like this: `claude --model sonnet --advisor opus` here's how it splits: → Sonnet 5 runs the session and writes the code → Haiku 5.5 explores files and docs in parallel → Opus 5.5 stays on call as advisor for the big decisions → you stop burning Opus context on tasks that don't need it Opus only steps in at three moments: → before a plan locks → when the same error hits twice → before calling it done Sonnet builds. Haiku explores. Opus reviews. JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split full tree > Sonnet 5 runs the main session and edits code > search maps the repo on Haiku 5.5 > grep finds call sites on Haiku 5.5 > docs pulls the API reference on Haiku 5.5 > Opus 5.5 on call as advisor, reads the full transcript when consulted > JEV routes micro-forks in milliseconds paste the tree and this prompt into Claude Code ↓ "Reconfigure my Claude Code setup around this tree: 1. Run the main session on Sonnet 5 with Opus 5.5 as advisor. 2. Create three read-only Haiku 5.5 subagents: search (maps the repo), grep (finds call sites), docs (pulls the API reference). 3. Add one rule to CLAUDE.md: consult the advisor before locking a plan, after the same error twice, and before calling a task done. 4. Route fast deterministic forks (tool choice, path selection, retries) through JEV. Show me every change as a diff first. No edits until I say go." ↳ save it, it'll come in handy

THIS IS PURE F*CKING PLATINUM Anthropic just shared a Claude Code setup that stops you from wasting expensive models on work cheaper ones can handle idea: let Sonnet write the code, Haiku handle the exploration, and Opus review the decisions that actually matter you just start Claude Code like this: `claude --model sonnet --advisor opus` here's how it splits: → Sonnet 5 runs the session and writes the code → Haiku 5.5 explores files and docs in parallel → Opus 5.5 stays on call as advisor for the big decisions → you stop burning Opus context on tasks that don't need it Opus only steps in at three moments: → before a plan locks → when the same error hits twice → before calling it done Sonnet builds. Haiku explores. Opus reviews. JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split full tree > Sonnet 5 runs the main session and edits code > search maps the repo on Haiku 5.5 > grep finds call sites on Haiku 5.5 > docs pulls the API reference on Haiku 5.5 > Opus 5.5 on call as advisor, reads the full transcript when consulted > JEV routes micro-forks in milliseconds paste the tree and this prompt into Claude Code ↓ "Reconfigure my Claude Code setup around this tree: 1. Run the main session on Sonnet 5 with Opus 5.5 as advisor. 2. Create three read-only Haiku 5.5 subagents: search (maps the repo), grep (finds call sites), docs (pulls the API reference). 3. Add one rule to CLAUDE.md: consult the advisor before locking a plan, after the same error twice, and before calling a task done. 4. Route fast deterministic forks (tool choice, path selection, retries) through JEV. Show me every change as a diff first. No edits until I say go." ↳ save it, it'll come in handy

Livsun

12,272 views • 14 days ago

Introducing Claude Sonnet 5, our most agentic Sonnet yet.

Introducing Claude Sonnet 5, our most agentic Sonnet yet.

Ado

54,484 views • 3 months ago

I think I want to eat Sonnet’s tree 🍊😂 Claude Sonnet 5.5 vs GPT-6.1 Sol I’m going with Sonnet this time. The mandarins look juicier, the greens feel more natural, and the colors are more realistic overall. And that soft, bouncy wobble when you shake the tree makes me want to poke it Sol did a pretty good job too, especially for the price. But next to Sonnet, its tree looks more like shiny plastic than jelly Estimated API cost: Sonnet - $10.74 Sol - $4.01 Almost 2.7x the price. Would you pay extra for this look? 👀

I think I want to eat Sonnet’s tree 🍊😂 Claude Sonnet 5.5 vs GPT-6.1 Sol I’m going with Sonnet this time. The mandarins look juicier, the greens feel more natural, and the colors are more realistic overall. And that soft, bouncy wobble when you shake the tree makes me want to poke it Sol did a pretty good job too, especially for the price. But next to Sonnet, its tree looks more like shiny plastic than jelly Estimated API cost: Sonnet - $10.74 Sol - $4.01 Almost 2.7x the price. Would you pay extra for this look? 👀

Vib3Coded

40,912 views • 23 days ago

THIS IS F*CKING BRILLIANT. Anthropic’s docs describe one of the smartest ways to run Opus three models work on one task and each does only the part it’s cheapest at. start Claude Code like this: claude -> model sonnet -> advisor opus you stop paying Opus prices for work that doesn’t need Opus > Sonnet runs the session and edits the code > Haiku 5.5 searches the repo and docs, at up to 40x less per token than Opus 5.5 > Opus waits as the advisor and reads the whole session, tool calls included Claude usually calls Opus at three points: > before it locks a plan > when the same error comes back > right before it says it’s done Sonnet drives. Haiku scouts. Opus signs off and if you go one step lower, most of an agent’s day is tiny choices like picking a file or a tool, or deciding whether to retry. Jev takes those first, so Sonnet and Opus only see the moments that are really open the whole setup Sonnet runs the main session Explore on Haiku 5.5 searches and pulls docs, read-only Opus on call as the advisor give Claude Code this setup and the prompt below ↓ “Set up my Claude Code exactly like this: Main model Sonnet, advisor Opus, saved as advisorModel in my settings. One read-only subagent named exactly Explore, on claude-haiku-5-5, to replace the built-in one. One line in CLAUDE.md: ask the advisor before locking a plan, after the same error twice, and before calling a task done, not more often. Check what could turn the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY) and only report it. Show every change as a diff first. Don’t edit anything until I say go.” before you turn it on: every advisor call re-reads the whole transcript with no cache. on a 200k session that’s about $0.80 in input, against $0.04 for a normal request. keep it to a few calls the built-in Explore agent runs on your main model unless a subagent is named exactly Explore. any other name does nothing turning the advisor on or off keeps your prompt cache. switching models rebuilds it it needs the Anthropic API, and it stays off if telemetry is disabled bookmark it before your next long session

THIS IS F*CKING BRILLIANT. Anthropic’s docs describe one of the smartest ways to run Opus three models work on one task and each does only the part it’s cheapest at. start Claude Code like this: claude -> model sonnet -> advisor opus you stop paying Opus prices for work that doesn’t need Opus > Sonnet runs the session and edits the code > Haiku 5.5 searches the repo and docs, at up to 40x less per token than Opus 5.5 > Opus waits as the advisor and reads the whole session, tool calls included Claude usually calls Opus at three points: > before it locks a plan > when the same error comes back > right before it says it’s done Sonnet drives. Haiku scouts. Opus signs off and if you go one step lower, most of an agent’s day is tiny choices like picking a file or a tool, or deciding whether to retry. Jev takes those first, so Sonnet and Opus only see the moments that are really open the whole setup Sonnet runs the main session Explore on Haiku 5.5 searches and pulls docs, read-only Opus on call as the advisor give Claude Code this setup and the prompt below ↓ “Set up my Claude Code exactly like this: Main model Sonnet, advisor Opus, saved as advisorModel in my settings. One read-only subagent named exactly Explore, on claude-haiku-5-5, to replace the built-in one. One line in CLAUDE.md: ask the advisor before locking a plan, after the same error twice, and before calling a task done, not more often. Check what could turn the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY) and only report it. Show every change as a diff first. Don’t edit anything until I say go.” before you turn it on: every advisor call re-reads the whole transcript with no cache. on a 200k session that’s about $0.80 in input, against $0.04 for a normal request. keep it to a few calls the built-in Explore agent runs on your main model unless a subagent is named exactly Explore. any other name does nothing turning the advisor on or off keeps your prompt cache. switching models rebuilds it it needs the Anthropic API, and it stays off if telemetry is disabled bookmark it before your next long session

rvaniaaa

62,223 views • 13 days ago

Fable 5.1 is 8x better than Fable 5 at controlling robot arms. It puts a block into a bowl 40% of the time, up from 5% (20 runs each), using 1.5x fewer tokens. 🧵

Fable 5.1 is 8x better than Fable 5 at controlling robot arms. It puts a block into a bowl 40% of the time, up from 5% (20 runs each), using 1.5x fewer tokens. 🧵

Jay Chooi

145,940 views • 1 month ago

we just made Claude Code - use 53% fewer tokens - respond 48% faster - give 3.2x better responses just by giving it a better grep

we just made Claude Code - use 53% fewer tokens - respond 48% faster - give 3.2x better responses just by giving it a better grep

Aamir

910,937 views • 11 months ago

Built one of my designs in code with Claude Sonnet 4.6

Built one of my designs in code with Claude Sonnet 4.6

Maxim Kuznetsov

39,192 views • 6 months ago

We just launched Claude Sonnet 4.5 and “Imagine with Claude”, a 5-day preview that creates dynamic experiences for you in real-time (and the first product I’ve worked on at Anthropic!). It pioneers the concept of “model-as-backend”, using a model to not only generate interfaces on the fly but also power all the functionality behind it – all made possible by our newest model, Claude Sonnet 4.5. Here’s a "choose your own adventure" version of my founder journey, as retold by Imagine with Claude:

We just launched Claude Sonnet 4.5 and “Imagine with Claude”, a 5-day preview that creates dynamic experiences for you in real-time (and the first product I’ve worked on at Anthropic!). It pioneers the concept of “model-as-backend”, using a model to not only generate interfaces on the fly but also power all the functionality behind it – all made possible by our newest model, Claude Sonnet 4.5. Here’s a "choose your own adventure" version of my founder journey, as retold by Imagine with Claude:

Sean Strong

115,727 views • 1 year ago

Fable 5 vs Sonnet on Arcads MCP Fable 5 is definitely smarter for video creation:

Fable 5 vs Sonnet on Arcads MCP Fable 5 is definitely smarter for video creation:

Romain Torres

374,807 views • 3 months ago