Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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 görüntüleme • 1 gün önce •via X (Twitter)

15 Yorum

Thariq profil fotoğrafı
Thariq1 gün önce

@pdrmnvd This is sick

lucas profil fotoğrafı
lucas1 gün önce

haiku 5.5 would make instant ui reality

Anshu profil fotoğrafı
Anshu1 gün önce

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

lucas profil fotoğrafı
lucas1 gün önce

true

Boris Cherny profil fotoğrafı
Boris Cherny1 gün önce

Super cool 🔥

air profil fotoğrafı
air1 gün önce

Wow! Tutorial please? 🙏

Anshu profil fotoğrafı
Anshu1 gün önce

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 profil fotoğrafı
Apo's T w itter1 gün önce

this is so cool

enji vi profil fotoğrafı
enji vi1 gün önce

Ayo this is so sool

valent profil fotoğrafı
valent1 gün önce

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

Nicholas Dunzelman profil fotoğrafı
Nicholas Dunzelman1 gün önce

dm'd you!

noel profil fotoğrafı
noel1 gün önce

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 profil fotoğrafı
Deon Holo1 gün önce

Lol the bug looks like a moving, gaping butthole.

Andre Buckingham 🧙‍♂️ profil fotoğrafı
Andre Buckingham 🧙‍♂️1 gün önce

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 profil fotoğrafı
Jeff Bruchado1 gün önce

please give failed tool calls the little cartoon fall sound

Benzer Videolar

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 görüntüleme • 2 gün önce