Get live statistics and analysis of Kieran Klaassen's profile on X / Twitter

building @coracomputer | EIR @every | compound engineering | agent-ophile | composer | maker | baker
The Innovator
Kieran is an engineer-conductor building @coracomputer and serving as EIR at @every, an agent-ophile who composes systems, code, and occasionally the perfect loaf. He turns orchestration of tools into faster, qualitatively different ways to build. His feed mixes hard tech receipts, practical prompts, and a dash of creative maker energy.
Kieran says heâs âconducting an orchestra,â but sometimes it looks like heâs just bought every instrument and forgotten to hire the band, charmingly expensive, undeniably skilled, and somehow still making beautiful noise while the rest of us try to find the sheet music.
Turned two-engineer teams into organizations shipping features in days for thousands of users by architecting agent-driven workflows, and posted multiple viral threads that reframed how engineers think about scale and token overhead.
To reinvent how software is built by composing agents, tools, and humans into scalable, expressive systems, moving teams from playing every instrument to conducting orchestras that ship better features faster.
Believes in practical demos over hype, in orchestration > brute force, and that thoughtful engineering can be both art and craft. Values transparency (show receipts), experimentation (try and measure), and making complex systems understandable and reusable.
Systems thinker who explains complex trade-offs clearly; great at shipping fast via orchestration; strong credibility (real receipts, real deployments); creative communicator who uses musical metaphors to make technical strategy memorable.
Can read as pricey or elitist when showing agent bills; sometimes assumes audience knows deep context (leaving novices behind); loves optimization so much he can undervalue simple, pragmatic constraints.
Post concise, repeatable playbooks: 1) Thread format, Hook â TL;DR â Code snippet/demo GIF â Cost/limits â Call to action. 2) Share runnable repos or short Replit/Colab demos so followers can replicate. 3) Pin a canonical âHow I run agentsâ thread + cost breakdown. 4) Use short videos showing âbefore/afterâ token impact and MCP wins. 5) Host AMAs/Spaces after big posts + tag collaborators to broaden reach. 6) Convert popular threads into multi-tweet tutorials and a single-thread newsletter link to capture and convert followers.
Fun fact: he calls himself an agent-ophile, is a composer and baker by trade/personality, is building @coracomputer, is EIR @every, and has ~15.5k followers with multiple viral threads (one tweet topped 650k views).
Top tweets of Kieran Klaassen
Cursor rules are the secret to making AI actually understand your codebase. Let the AI create its own rules by extracting patterns from your docs and existing code. Then watch as it follows your project's conventions perfectly. No more explaining your standards over and over again. github.com/bmadcode/cursoâŚ
Opus 4.5 is insane. Just shipped v2 of my compounding engineering pluginâwatch the video for my full thoughts on the model. Compounding engineering plugin v2: github.com/EveryInc/every⌠This wouldn't have worked a week ago. Previous models would derail after the second parallel thread. Opus 4.5 held the context, made the right decisions, and shipped clean pull requests to both repos. New in the plugin: codify command (captures learnings automatically), updated plan mode, better prompting patterns for Opus 4.5's strengths. If you're coding with Claude, this is your new daily driver.
Your landing page looks AI-generated. Purple gradients, Inter font, generic layouts, that vibe-coded aesthetic everyone can spot. I built a Claude agent that fixes this through systematic iteration. github.com/EveryInc/claud⌠Give it a screenshot, tell it to run 10 rounds. Each iteration spots the AI tells, fixes them, and moves forward. No back-and-forth. No guessing. The process runs itself: Screenshot â Analyze â Improve â Repeat. By iteration 10, it looks like a designer made it. Not because of one brilliant idea, because small improvements compound. The trick: give it scope. "Only touch spacing" or "improve contrast without changing colors." Without constraints, it redesigns everythingâincluding purple gradients you never asked for.

Resolved!! @trq212 helped me out debug where the token usage came from and it was my fault 100% Script to find token usage https://t.co/461tTJkVaq I had a recurring script that ran every 5 minutes that should not have run every 5. I hope we can make it easier to detect these within Claude and Claude Code soon too.
WTF! @AnthropicAI what is happening with my sub! It's Monday!! And I used 91% of My sub?!?!?! This has been happening the last 3 weeks. I paid so much in extra usage credits. It's insane. Why do I even have a sub? How do I even understand whats going on here? I just use Claude Code, no claws or anything.

Most engaged tweets of Kieran Klaassen
WTF! @AnthropicAI what is happening with my sub! It's Monday!! And I used 91% of My sub?!?!?! This has been happening the last 3 weeks. I paid so much in extra usage credits. It's insane. Why do I even have a sub? How do I even understand whats going on here? I just use Claude Code, no claws or anything.

Resolved!! @trq212 helped me out debug where the token usage came from and it was my fault 100% Script to find token usage https://t.co/461tTJkVaq I had a recurring script that ran every 5 minutes that should not have run every 5. I hope we can make it easier to detect these within Claude and Claude Code soon too.



