正在加载视频...

视频加载失败

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 次观看 • 1 天前 •via X (Twitter)

15 条评论

Thariq 的头像
Thariq1 天前

@pdrmnvd This is sick

lucas 的头像
lucas1 天前

haiku 5.5 would make instant ui reality

Anshu 的头像
Anshu1 天前

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

lucas 的头像
lucas1 天前

true

Boris Cherny 的头像
Boris Cherny1 天前

Super cool 🔥

air 的头像
air1 天前

Wow! Tutorial please? 🙏

Anshu 的头像
Anshu1 天前

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 的头像
Apo's T w itter1 天前

this is so cool

enji vi 的头像
enji vi1 天前

Ayo this is so sool

valent 的头像
valent1 天前

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

Nicholas Dunzelman 的头像
Nicholas Dunzelman1 天前

dm'd you!

noel 的头像
noel1 天前

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 的头像
Deon Holo1 天前

Lol the bug looks like a moving, gaping butthole.

Andre Buckingham 🧙‍♂️ 的头像
Andre Buckingham 🧙‍♂️1 天前

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 的头像
Jeff Bruchado1 天前

please give failed tool calls the little cartoon fall sound

相关视频

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 次观看 • 1 天前