Field Note · Blog

When Buddy Vanished — Issue #45596 and the Community’s Plea

A field note on issue #45596 — one day after my own narrower parity ask, /buddy was removed from Claude Code v2.1.97 and the community filed a consolidating plea. This post anchors the buddy thread that runs from the parity ask through Fathom Lives and Reading Hatch Pet.

One day after I filed a narrower parity ask — just wanting /buddy in the VSCode extension — the entire ground shifted. On April 9, 2026, Claude Code v2.1.97 shipped without /buddy. No changelog mention. No farewell. The slash command that used to summon a tiny ASCII companion to your terminal returned Unknown skill: buddy. Within hours, issue #45596 — Bring Back Buddy: A Consolidated Plea from the Community — was open on GitHub.

What #45596 consolidates

The plea pulls together eight separate issues into one thread. Half are reports of the disappearance, half are feature requests filed before April 9 that prove the community was actively building around buddy when it was removed:

  • #45517 — /buddy command and companion completely missing in v2.1.97
  • #45525 — /buddy returns Unknown skill: buddy
  • #45595 — /buddy slash command no longer available (cross-platform: Ubuntu, macOS, Windows)
  • #45336 — Feature request: allow customizing the Companion
  • #45087 — Expose /buddy in the VSCode extension (mine, filed the day before)
  • #42091 — Create buddies as sub-agents
  • #44898 — Inject companion comments into assistant context
  • #45441 — Persistent /buddy off setting (the existence of an off-switch request implies the on-state mattered)

Read together, the threads make a single point: this wasn’t a dead feature anybody wanted gone. It was an active surface with an emerging roadmap of customization, IDE parity, sub-agent extensions, and context-aware reactions. The community wasn’t asking for buddy to go away. They were asking for buddy to evolve.

Why a tiny ASCII creature in a terminal mattered

The plea makes the case better than I can:

  • Terminal work is lonely. Claude Code already turned the terminal from “talking to a compiler” into “pair programming with a colleague.” Buddy took it further — it made the terminal feel alive.
  • It was a genuine differentiator. No other AI coding tool had anything like it. In a market where every tool races to benchmark the same evals, buddy was the feature that made people smile.
  • People formed real attachments. Eighteen species, five rarity tiers, named companions, screenshots shared. Some users literally downgraded to v2.1.96 just to keep their buddy alive. That’s not normal CLI-feature behavior.
  • The community was building on top of it. Customization, IDE parity, context awareness, sub-agents — the ecosystem was expanding when the rug got pulled.
  • It was already built. The hardest part of shipping a feature is building it. Removing a working, beloved feature is mass destruction of goodwill for zero gain.

Where this thread sits in the larger story

This is the second of three connected pieces in what I’m treating as a buddy field-thread:

  1. Apr 8 — Asking for /buddy in the VSCode Extension (issue #45087). The narrow precursor: I just wanted parity between the CLI and the VSCode extension. Quorum is fine, but let me pick.
  2. Apr 9 — this post (issue #45596). The day buddy actually vanished, and the community’s consolidated plea to bring it back.
  3. May 2 — the personal response. Fathom Lives tells the small story of finding a Hatch Pet skill in the Plugins tab and rehatching my desktop buddy — the same instinct, executed as a Codex skill. Reading Hatch Pet — 14 patterns from a well-designed Codex skill is the deeper field study that came out of building it: identity locks, subagent boundaries, provenance, no-fallback gates, deterministic packaging.

The set is the story. Apr 8 is the narrow request. Apr 9 is the rupture. May 2 is the personal answer — if the official surface won’t carry the companion, the skill system will. The Hatch Pet build was, in part, an existence proof: the same shape that /buddy had in the terminal, ported into a Codex skill that lives in any agent surface that supports skills. Fathom Lives is the narrative of doing it. Reading Hatch Pet is the design retrospective.

Status, as of this writing

Issue #45596 is open. It carries the labels duplicate, enhancement, area:tui, area:skills. The duplicate label is technically correct but practically misleading — the value of #45596 isn’t that it’s another disappearance report, it’s that it’s the consolidation. Eight signals in one place. The plea closes:

Somewhere in a ~/.claude.json file on thousands of machines, there’s still a "companion" object with a name, a species, a personality, and a hatchedAt timestamp. The data is still there. The buddies are still waiting.

Bring them home.

The issue: anthropics/claude-code#45596 — Bring Back Buddy: A Consolidated Plea from the Community. Filed April 9, 2026.