What
The /feedback
Evidence
Provider-specific feedback disabling (search for "/feedback has been disabled" and "/feedback is not available when using")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
How sure we are
One source agrees One thing we can check says the same as this entry.
Anthropic's release notes agree /feedback now explains why it's unavailable instead of disappearing from the slash menu
See this entry in the whole of v2.1.91 →
Names in this entry
slash /feedback Send product feedback about Claude Code. Opens the same dialog as /bug, with the same consent step, sending rules, and mid-turn behavior. In sessions with Claude-drafted feedback , /feedback with no argument opens the drafts queue instead, where you review, edit, send, or discard the drafts Claude queued; the queue includes an option to write a new report in the dialog. With an argument, and for /bug always, the dialog opens directly
env DISABLE_FEEDBACK_COMMAND Feedback and bug-report commands are hidden when Claude Code runs through the SDK.
env DISABLE_BUG_COMMAND Temporary probes that checked whether old code paths still ran have been deleted; behaviour is unchanged.
env CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC Set to any non-empty value, such as 1, to disable nonessential network traffic: auto-updates, telemetry, error reporting, the /feedback command, Claude-drafted feedback , release notes, the PR and MR status badge checks, and availability checks such as the fast mode check. It also stops the background runs of plugin command sources , which are local commands rather than network traffic, because they can trigger dependency installs. Setting it to 0 or false still disables this traffic , unlike most on/off variables; unset the variable to allow it again. Also disables feature-flag fetching, which makes Remote Control and the other features that need feature-flag fetching unavailable. Official plugin marketplace auto-install isn't covered; disable it with CLAUDE_CODE_DISABLE_OFFICIAL_MARKETPLACE_AUTOINSTALL. Doesn't affect gateway model discovery , which has its own opt-in
Anthropic's note
Upstream's own release notes for v2.1.91 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.
/feedback
Is this right?
0 0 Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
← Previous · 1 of 29
Disable Shell Execution in Skills (Policy Setting)
In v2.1.91 Changes release-page order
Next → · 3 of 29
Peer Session Messaging
