Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Bring back /buddy as a permanent (or opt-in) feature [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46326•Fetched 2026-04-11 06:23:14
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
3
Author
ChrisMafiaMDChrisMafiaMD
Participants
ChrisMafiaMDChrisMafiaMD
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

What happened

The /buddy feature shipped in v2.1.88 as an April Fools' Day easter egg — "hatch a small creature that watches you code." It was removed in a later release.

Why it matters

Despite being a joke feature, /buddy turned out to be genuinely useful:

  • Faster CLI learning curve — the buddy's prompts and reactions guided me to features I wouldn't have discovered on my own
  • Early issue detection — it surfaced insights about my code while I was working, helping me spot problems sooner
  • Higher engagement — the companion aspect made longer coding sessions more enjoyable and kept me coming back to the CLI more often

Request

I'd love to see /buddy return as a permanent or opt-in feature. It doesn't have to be the exact April Fools' version — even a streamlined "coding companion" mode that watches your session and offers periodic insights would be valuable.

The fact that a "joke" feature improved my productivity and learning says something worth paying attention to.

extent analysis

TL;DR

The /buddy feature should be reconsidered as a permanent or opt-in feature due to its unexpected benefits in improving the CLI learning curve, issue detection, and user engagement.

Guidance

  • Reevaluate the /buddy feature's removal and consider its potential as a valuable tool for users.
  • Gather more feedback from users who interacted with the /buddy feature to understand its impact and identify areas for improvement.
  • Explore the possibility of creating a streamlined "coding companion" mode that offers periodic insights and guidance.
  • Consider adding an opt-in setting to allow users to choose whether they want to use the feature, addressing potential concerns about its usefulness.

Notes

The request is based on the user's positive experience with the /buddy feature, which was initially intended as a joke. The feature's benefits in improving productivity and learning are worth exploring further.

Recommendation

Apply workaround: Reconsider and potentially reimplement the /buddy feature as a permanent or opt-in option, focusing on its benefits in enhancing user experience and productivity.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#tool integration#LLM response#prompt template#agent execution#callback error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Bring back /buddy as a permanent (or opt-in) feature [1 participants]