Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /feedback command still appears when DISABLE_FEEDBACK_COMMAND=1 is set

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…

Code Example

{
     "env": {
       "DISABLE_FEEDBACK_COMMAND": "1"
     }
   }
RAW_BUFFERClick to expand / collapse

Bug Description

The /feedback slash command remains visible and usable even when DISABLE_FEEDBACK_COMMAND is set to "1" in the project-level settings file.

Steps to Reproduce

  1. Set DISABLE_FEEDBACK_COMMAND to "1" in the env block of a project-level settings.json: 
    {
  "env": {
    "DISABLE_FEEDBACK_COMMAND": "1"
  }
}
  2. Restart Claude Code
  3. The /feedback command still appears in the slash command list

Environment

  • The env var is confirmed present in the shell environment (echo $DISABLE_FEEDBACK_COMMAND returns 1)
  • Settings are loaded from a custom $CLAUDE_CONFIG_DIR (project-level settings.json)
  • macOS, installed via Homebrew

Expected Behavior

The /feedback slash command should not appear when DISABLE_FEEDBACK_COMMAND=1.

Actual Behavior

The /feedback command is still listed and functional despite the env var being set and confirmed in the environment.

extent analysis

TL;DR

The /feedback slash command remains visible due to a potential issue with environment variable handling or settings loading in the Claude Code application.

Guidance

  • Verify that the DISABLE_FEEDBACK_COMMAND environment variable is correctly loaded and accessible within the Claude Code application, beyond just the shell environment.
  • Check the application's documentation or source code to ensure that the DISABLE_FEEDBACK_COMMAND variable is correctly handled and applied to disable the /feedback command.
  • Confirm that the settings.json file is being loaded correctly from the specified $CLAUDE_CONFIG_DIR and that the env block is properly parsed.
  • Test whether setting DISABLE_FEEDBACK_COMMAND directly in the operating system's environment variables (outside of the settings.json file) has any effect on the visibility of the /feedback command.

Example

No specific code example is provided due to the lack of direct code references in the issue description.

Notes

The issue might be related to how environment variables are handled within the Claude Code application or how settings are loaded from the settings.json file. Without more information about the application's internal workings, it's challenging to provide a definitive solution.

Recommendation

Apply a workaround by directly modifying the application's configuration or code to explicitly check for and honor the DISABLE_FEEDBACK_COMMAND environment variable, if possible, as the root cause of the issue is not immediately clear.

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…
#memory management#API rate limit#retriever error#indexing error#inference speed

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 /feedback command still appears when DISABLE_FEEDBACK_COMMAND=1 is set