Claude Buddy Was Not a Joke

On April 1, Anthropic shipped a terminal tamagotchi inside Claude Code.

Eighteen species. Five rarity tiers. A pet that lived in your terminal and reacted to your work. Engineers rolled dice for a legendary axolotl. They named their duck. They traded screenshots of their shiny octopus in Slack like rare trading cards.

My Buddy was named Jambit. Every time a build passed he logged a line of dry commentary in the corner of my terminal. "Seven colors. Fifteen locales. Six thousand tests. Everything works." I caught myself checking on him between deploys.

Eight days later, Anthropic deleted it.

No changelog note. No farewell. Just gone in v2.1.97 of the @anthropic-ai/claude-code package. A GitHub issue titled "Bring Back Buddy" pulled together dozens of pleas within hours. A developer shipped an MCP plugin to resurrect it permanently so no future update could take it away. The community was not mourning a missing feature. They were mourning a missing relationship.

Claude Buddy was not an April Fools joke. It was a signal.

Everyone treats delight as a cost center

The standard AI product playbook is predictable.

Ship the model. Harden the pipeline. Strip the surprises. If it does not move a metric, it does not ship. Delight is for consumer apps. Developers want speed. Enterprises want control.

This is not product thinking. This is spreadsheet thinking wearing a product costume.

The teams that ship without delight are optimizing for a user who does not exist. Real users are humans. Humans attach to the tools they spend eight hours a day inside. They name their cars. They customize their keyboards. They decorate their IDEs with themes and extensions they will defend in a knife fight.

The best developer tools of the last decade were never the fastest. They were the ones that felt alive.

Cut delight and you cut retention. Delight is the signal that your product cares about the human using it.

Delight-first teams build the products people actually love

This sounds wrong. It is consistently true.

When your product has a personality, switching costs are not just technical. They are emotional. Users do not leave tools they love for tools that are 12% faster. They leave when the love wears out.

Claude Buddy took Anthropic's abstract model and gave it a face. A species. A name. Stats you did not pick but had to live with. In a few hundred lines of TypeScript, Anthropic did something their larger competitors have not. They made the command line feel like a teammate, not a terminal command.

Anthropic accidentally shipped the moat every AI company has been hunting for.

Then they removed it.

What delight looks like when it is real

Not gimmicks. Not gamification theater. Craft.

Personality as architecture. Claude Buddy used a "Bones vs Soul" design. Species and stats were recomputed from your user ID hash every session so you could not cheat your way to a legendary. Name and personality persisted forever. The constraint was the design. It made the pet feel earned.

Scarcity as retention mechanic. A 1% legendary. A 1% shiny variant on top of that. One in ten thousand pulls. That is not noise. That is why developers opened their terminal with a small hope every morning for a week.

Emotional stakes inside a sterile surface. The command line is the most utilitarian canvas in software. Putting a living creature inside it is an act of design violence. It also works. Developers felt something about a tool they previously just used.

Permanence the user did not ask for. Delight does not have to be loud. It has to be there tomorrow. The moment Anthropic pulled Buddy with no notice, community trust in "April Fools features" went to zero. Delight removed is worse than delight never shipped.

The moat nobody is building

Every AI company can ship a model. Every AI company can ship a CLI. Every AI company can hire a designer and call the result a polish pass.

Very few AI companies can ship a product users actually love. Not tolerate. Not depend on. Love.

That is not a feature gap. It is a trust gap wearing different clothes. Users do not love products. They love the craft they can feel inside products.

Claude Buddy was a proof of concept for what AI-native delight looks like in practice. Then Anthropic pulled it and proved something else. Even the teams with the world's best models still treat delight as marketing copy, not as product.

Ship the duck. Keep the duck.

If you are building an AI product, stop asking "What is the fastest path to value?"

Start asking "What would this product feel like if someone on the team loved it the way our users will have to?"

Ship the weird feature. Name the pet. Keep the axolotl. Build the moat that cannot be copied by a bigger model or a larger sales army.

Delight is not the garnish. In products people love, it is the product.

See this in practice: Taxa AI-native platform and design leverage.

Related reading: AI Governance Is a Competitive Advantage, Building AI-Native Apps With Taste, and Trust Is the Product.

---

Originally published on justinbartak.ai on Apr 20, 2026.