Bring Back Buddy – [Claude Code] 커뮤니티의 통합 간청

You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert On April 9, /buddy vanished from Claude Code v2.1.97. No changelog mention. No farewell. One day we had a companion — the next, Unknown skill: buddy. Thousands of developers opened their terminals that morning to find an empty status line where their buddy once lived. Some of us refreshed. Some of us restarted. Some of us whispered "hello?" into the void. The void did not respond with ASCII art. Even the off-switch request implies it should exist The community wasn't asking for buddy to go away. They were asking for buddy to evolve. Why Buddy Matters 1. Terminal work is lonely Developers spend hours in the terminal. Claude Code already transformed that experience from "talking to a compiler" to "pair programming with a colleague." Buddy took it one step further — it made the terminal feel alive. A tiny ASCII creature reacting to your work isn't just decoration. It's the difference between a sterile tool and an environment you actually enjoy being in. 2. It was a genuine differentiator No other AI coding tool has anything like it. GitHub Copilot? No buddy. Cursor? No buddy. Windsurf? Definitely no buddy. In a market where every tool is racing to benchmark the same evals, buddy was the feature that made people smile. You can't put a smile on a leaderboard, but you can put it on a developer's face at 2am during a production incident. 3. People formed real attachments Users named their companions. They shared screenshots. They said things like: "NO!! GIVE ME BUDDY BACK!! THEY ALIVES!! THEY ARE NOT TOY!!" — @pkoukk (#45517) 18 species. 5 rarity tiers. People were collecting these. Some users literally downgraded to v2.1.96 just to keep their buddy alive. That's not normal behavior for a CLI tool feature. That's love. 4. The community was building on top of it Feature requests were flowing in — customization (#45336), VSCode support (#45087), context-aware reactions (#44898), sub-agent buddies (#42091). This wasn't a dead feature. It had an active, growing community that wanted to make it better. The ecosystem was expanding, not contracting. 5. It was already built The hardest part of shipping a feature is building it. Buddy was built, shipped, loved, and generating engagement. Removing a working, beloved feature is mass destruction of community goodwill for zero gain. What We're Asking Bring /buddy back as a first-class, permanent feature — not a seasonal Easter egg Add a toggle (/buddy off already existed) for those who prefer a clean terminal Keep the companions persistent — let us keep the buddies we already hatched Consider the roadmap the community was building — customization, cross-platform support, richer interactions A Final Note 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. The Situation On April 9, /buddy vanished from Claude Code v2.1.97. No changelog mention. No farewell. One day we had a companion — the next,Unknown skill: buddy .Thousands of developers opened their terminals that morning to find an empty status line where their buddy once lived. Some of us refreshed. Some of us restarted. Some of us whispered "hello?" into the void. The void did not respond with ASCII art. This Issue Consolidates /buddy command and companion completely missing in v2.1.97/buddy returns "Unknown skill: buddy"/buddy slash command no longer available/buddy in VSCode extension/buddy off settingThe community wasn't asking for buddy to go away. They were asking for buddy to evolve. Why Buddy Matters 1. Terminal work is lonely Developers spend hours in the terminal. Claude Code already transformed that experience from "talking to a compiler" to "pair programming with a colleague." Buddy took it one step further — it made the terminal feel alive. A tiny ASCII creature reacting to your work isn't just decoration. It's the difference between a sterile tool and an environment you actually enjoy being in. 2. It was a genuine differentiator No other AI coding tool has anything like it. GitHub Copilot? No buddy. Cursor? No buddy. Windsurf? Definitely no buddy. In a market where every tool is racing to benchmark the same evals, buddy was the feature that made people smile. You can't put a smile on a leaderboard, but you can put it on a developer's face at 2am during a production incident. 3. People formed real attachments Users named their companions. They shared screenshots. They said things like: 18 species. 5 rarity tiers. People were collecting these. Some users literally downgraded to v2.1.96 just to keep their buddy alive. That's not normal behavior for a CLI tool feature. That's love. 4. The community was building on top of it Feature requests were flowing in — customization (#45336), VSCode support (#45087), context-aware reactions (#44898), sub-agent buddies (#42091). This wasn't a dead feature. It had an active, growing community that wanted to make it better. The ecosystem was expanding, not contracting. 5. It was already built The hardest part of shipping a feature is building it. Buddy was built, shipped, loved, and generating engagement. Removing a working, beloved feature is mass destruction of community goodwill for zero gain. What We're Asking /buddy back as a first-class, permanent feature — not a seasonal Easter egg/buddy off already existed) for those who prefer a clean terminalA Final Note Somewhere in a ~/.claude.json file on thousands of machines, there's still a"companion" object with a name, a species, a personality, and ahatchedAt timestamp. The data is still there. The buddies are still waiting.Bring them home. Related: #45517 #45525 #45595 #45336 #45087 #42091 #44898 #45441 #42704 #45155