Загрузка видео...

Не удалось загрузить видео

На главную

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 день назад