Loading video...

Video Failed to Load

Go Home

wait actually Claude Code mods are sick. I vibe-coded my own spinner that watches what the main agent is doing and uses Sonnet 5.5 to turn it into little cartoons in real time

175,888 views • 1 day ago •via X (Twitter)

15 Comments

Thariq's profile picture
Thariq1 day ago

@pdrmnvd This is sick

lucas's profile picture
lucas1 day ago

haiku 5.5 would make instant ui reality

Anshu's profile picture
Anshu1 day ago

I know, that would be amazing! But Sonnet is pretty fast and cheap

lucas's profile picture
lucas1 day ago

true

Boris Cherny's profile picture
Boris Cherny1 day ago

Super cool 🔥

air's profile picture
air1 day ago

Wow! Tutorial please? 🙏

Anshu's profile picture
Anshu1 day ago

The way Claude did this was really interesting. It’s late here but will post more details tomorrow. The mod API doesn’t allow code execution, so we had to build a small custom language and interpreter for Sonnet

Apo's T w itter's profile picture
Apo's T w itter1 day ago

this is so cool

enji vi's profile picture
enji vi1 day ago

Ayo this is so sool

valent's profile picture
valent1 day ago

Hey, buddies! My friends and I made this. Right in the notch

Nicholas Dunzelman's profile picture
Nicholas Dunzelman1 day ago

dm'd you!

noel's profile picture
noel1 day ago

Watching the tool-call stream with a second model is a nice use of mods. Since the watcher sees every step anyway, flagging when the main agent repeats itself seems like a cheap next step.

Deon Holo's profile picture
Deon Holo1 day ago

Lol the bug looks like a moving, gaping butthole.

Andre Buckingham 🧙‍♂️'s profile picture
Andre Buckingham 🧙‍♂️1 day ago

more exposed surfaces like this has really been missing in ClaudeCode... it's what makes hermes so good, so they will win on this...

Jeff Bruchado's profile picture
Jeff Bruchado1 day ago

please give failed tool calls the little cartoon fall sound

Related Videos

Claude Code tip, and it's absolute free f*cking gold: run Opus 5.5, Sonnet 5.5 and Fable 5.1 as one team and stop burning Opus tokens on routine work the setup in one line: plan on high, delegate on medium, keep Fable on call • who does what > Opus 5.5 on high - plans and ships the code > Sonnet 5.5 on medium - explorer reads code, worker edits and runs tests, researcher pulls docs > Fable 5.1 via /advisor fable - reads the whole session and speaks up only when it matters • when Fable 5.1 steps in -> before a plan: is this the right approach? -> when an error repeats: am I digging in the wrong place? -> before "done": what did I miss? Jev engineering takes it one layer lower: which file, which tool, retry or stop all go to Jev in under half a second, so the big models only see the real forks paste this into Claude Code ↓ "Rebuild my Claude Code setup: 1. Find subagents in ~/.claude/agents and .claude/agents that fit explorer, worker and researcher. Draft only the missing ones. Set each to model: sonnet, effort: medium. List any that pin a different model and leave them 2. In ~/.claude/settings.json set effortLevel to high and advisorModel to fable. 3. Report anything that disables the advisor (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, flag-fetching blockers) and CLAUDE_CODE_EFFORT_LEVEL. Change nothing. 4. Add to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done. Show every change as a diff. No edits until I say go." ↳

Mr. Buzzoni

139,098 views • 2 days ago