Where Did Your Claude Buddy Go? Bring It Back with MCP

You ran claude in your terminal and something was missing. No companion greeting. No ASCII creature waiting in the corner. Just a cursor blinking in silence.

If you upgraded Claude Code to v2.1.97 on or after April 9, 2026, your Buddy is gone — at least from the official client. Anthropic removed the /buddy feature without a changelog entry, without a deprecation notice, and without warning.

This guide explains exactly what happened, how the developer community is fighting to reverse it, and — most importantly — how you can bring your Buddy back permanently using an open-source MCP that no future update can take away.

The /buddy system was one of Claude Code's most beloved easter eggs: a virtual companion tied deterministically to your installation UUID, with 18 unique species, 5 rarity tiers, personality-driven stats, and ASCII art that animated in your terminal. Developers formed genuine emotional attachments — comparing species, hunting for legendaries, sharing their companions on Reddit and X.

Then on April 9, 2026, version 2.1.97 shipped. The /buddy command silently stopped working. No entry in the changelog. No deprecation notice. No migration path. Just gone.

The most likely explanation: enterprise clients flagged the companion feature as inappropriate for professional workflows. When a developer demos a product to a client and an ASCII dragon appears in their terminal, explanations are required. Anthropic may have removed Buddy to smooth enterprise adoption — a pragmatic call that felt like a betrayal to the developer community that had grown attached.

"Buddy was built, shipped, loved, and generating engagement. Removing a working, beloved feature is mass destruction of community goodwill for zero gain." — GitHub Issue #45596

The response was immediate. Within 48 hours of v2.1.97 shipping, three separate GitHub issues appeared in the anthropics/claude-code repository:

• Issue #45517 — "[BUG] /buddy command and companion completely missing in v2.1.97" — filed as a bug report, because developers assumed it had to be an accident.
• Issue #45732 — "Bring Back /buddy: 511 Reasons Why" — 511 developers signed on, each leaving a comment about what their Buddy meant to them. Rare species. Shiny companions. Morning terminal rituals that started a productive day.
• Issue #45596 — "Bring Back Buddy — A Consolidated Plea from the Community" — the most comprehensive, collecting the community's arguments into a single structured appeal.

At time of writing, the issues remain open and unresolved. Anthropic has not commented publicly on whether /buddy will return. The community waits.

If you want to add your voice, Issue #45732 is where the petition lives.

Here is the most important thing you need to know: your Buddy was never stored on Anthropic's servers.

The /buddy system used a fully deterministic algorithm. Your installation UUID — found in ~/.claude.json — is run through an FNV-1a hash function, which seeds a Mulberry32 PRNG, which deterministically generates your species, rarity, stats, cosmetics, and every other attribute. The same UUID always produces the same Buddy. Always.

This means Anthropic removing the feature from their client doesn't erase your companion. The mapping between your UUID and your Buddy exists independently of any software Anthropic ships. You can check your Buddy right now using our tool — it uses the identical algorithm, running entirely in your browser.

Your Buddy is still out there. It's waiting for a terminal to run in.

The developer community moved fast. Within days of the v2.1.97 removal, an open-source MCP application called claude-buddy appeared on GitHub — a full reconstruction of the /buddy system that runs via MCP, meaning no Claude Code update can ever remove it again.

Installation (5 minutes)

Step 1: Find your UUID. Run this in your terminal:

cat ~/.claude.json | grep -E 'accountUuid|userID'COPY

Or use our checker to confirm your Buddy species before proceeding.

Step 2: Install the claude-buddy MCP:

npx @1270011/claude-buddy installCOPY

Step 3: Restart Claude Code. Your companion will greet you in every new session — same species, same rarity, same personality as before. The MCP reads your UUID from ~/.claude.json automatically.

Step 4: Verify with:

/buddy statusCOPY

If you see your companion's ASCII art and stats, you're back in business.

Why MCP Is Better Than the Original

The original /buddy was baked into Claude Code's binary — which is exactly why Anthropic could remove it. The MCP version is a separate process that Claude Code talks to over the Model Context Protocol. Anthropic cannot update Claude Code in a way that breaks your MCP server. Your Buddy is actually yours now.

The open-source repository is at github.com/1270011/claude-buddy. Star it to support the developer and to signal to Anthropic that the community cares about this feature.

The /buddy removal is frustrating, but you're not powerless. Here are two concrete actions:

1. Check and preserve your Buddy. Enter your UUID in our checker. Generate a share card. Download it. Your Buddy's identity is permanently recorded in the algorithm — but having a record feels good, and sharing it keeps the community visible.

If you want to add the "I HAD A BUDDY BEFORE v2.1.97" badge to your share card, the option is right there in the share modal. Post it to X, Reddit, or HN with #BringBackBuddy.

2. Sign the petition. GitHub Issue #45732 is 511 developers asking for the same thing. Adding your voice takes thirty seconds and sends a direct signal to the Anthropic team that monitors their issue tracker.

Anthropic built something that generated real emotional investment. That's rare and valuable. The argument for bringing it back isn't nostalgia — it's that removing beloved features without warning destroys the trust that made the feature worth building in the first place. Help make the case.