Under the hood
/feedback command now respects the org-level allow_product_feedback policy
What
The /feedback command, along with other feedback-related UI, is now gated by a new helper that checks the organization policy allow_product_feedback. This is the same policy already used to hide feedback surfaces for organizations under ZDR (zero data retention) or HIPAA restrictions.
Why
This keeps /feedback consistent with other feedback surfaces, so organizations that have disabled product feedback for compliance reasons won't see the /feedback command available either.
Names in the bundle/feedback
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Use Claude Code in VS Code touched a line naming /feedback after this was published.
If your organization's policy turns product feedback off, **Report a problem** doesn't appear in the menu, and `/bug` and `/feedback` show a `Feedback is turned off by your organization's policy or this environment's settings.` notice inst…vs-code see the edit
Confirmed since
Anthropic's documentation has since written up /feedback, on Claude Code changelog.
* Changed `/bug` and `/feedback` reports to include only model-behavior params (model, system prompt, tools) from the last API request, omitting request metadata and `CLAUDE_CODE_EXTRA_BODY` fieldschangelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /feedback, on Claude Code changelog.