claude-code - 💡(How to fix) Fix Feature request: persistent /buddy off setting in settings.json [1 comments, 2 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#45441Fetched 2026-04-09 08:05:21
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

Fix Action

Workaround

Currently the only workaround is to add an instruction to CLAUDE.md asking Claude to run /buddy off at session start, which is fragile and relies on Claude reading and acting on the file rather than a hard config setting.

RAW_BUFFERClick to expand / collapse

Feature Request

The /buddy companion feature introduced for April 1st auto-starts on every new session. Running /buddy off mutes it for the current session only — there is no way to permanently disable it.

Requested Change

Please add a persistent setting to settings.json (e.g. "buddyEnabled": false) that permanently disables the companion without needing to run /buddy off at the start of every session.

Workaround

Currently the only workaround is to add an instruction to CLAUDE.md asking Claude to run /buddy off at session start, which is fragile and relies on Claude reading and acting on the file rather than a hard config setting.

Why

For users who don't want the companion at all, having to mute it every session is friction that a simple config flag would eliminate.

extent analysis

TL;DR

Add a "buddyEnabled": false setting to settings.json to permanently disable the companion feature.

Guidance

  • Consider adding a new configuration option to settings.json to store the user's preference for enabling or disabling the companion feature.
  • Consider implementing a check at the start of each session to read the buddyEnabled setting from settings.json and disable the companion feature if it is set to false.
  • Evaluate the current workaround of adding an instruction to CLAUDE.md and assess its reliability and potential for errors.
  • Investigate how to handle cases where the user wants to enable the companion feature after it has been permanently disabled.

Example

{
  "buddyEnabled": false
}

This example shows how the settings.json file could be updated to include the new configuration option.

Notes

The implementation details of the companion feature and the settings.json file are not provided, so the exact steps to add the new configuration option may vary.

Recommendation

Apply workaround: Add a "buddyEnabled": false setting to settings.json to permanently disable the companion feature, as this is a straightforward and effective solution to the problem.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING