Claude Code has updated with another quite interesting little feature.
This time, it can help you draft feedback reports.
When a certain feature malfunctions, when Claude realizes it made a mistake, or when you point out where something went wrong, it will automatically compile the relevant situation into a report.
You can review, edit it before sending, and decide whether to approve submission.
However, you can also disable this feature in /config, or modify its behavior settings.
The official team has also compiled detailed documentation; let's take a look at the specific content.
Claude Code Starts 'Writing Feedback Reports' for Itself
Feedback drafted by Claude is a report about Claude Code written by Claude on your behalf. This feature requires using Claude Code v2.1.238 or later.
Claude Code saves each feedback draft on your local device, at the path: ~/.claude/feedback/drafts/. Nothing is sent to Anthropic until you actively send it.
Specifically, Claude will automatically draft feedback via the SendFeedback tool in the following situations:
- A tool or command continuously fails;
- Claude cannot complete a certain request you made;
- You point out that Claude made a mistake, or Claude itself realizes it made an error;
- You ask Claude to submit feedback.
Documentation address:
https://code.claude.com/docs/en/tools-reference#sendfeedback-tool-behavior
What You See When Claude Drafts Feedback
When Claude queues a feedback draft, you will see a card above the input box, displaying the title of that draft. You can:
- Press 1 to view the draft;
- Press 2 twice in a row to send it as-is directly;
- Press 0 to ignore this card.
Even if you ignore the card, the draft will remain in the feedback queue.
After you ignore a feedback card, Claude Code will ask if you want to turn off Claude's automatic feedback drafting feature. If you choose not to turn it off twice in a row, it will stop asking afterwards.
By default, a maximum of 3 feedback cards are displayed per session.
After exceeding this limit, or when you set feedbackDrafts to quiet, only the number of feedback drafts currently queued will be shown at the bottom of the input box, and no specific cards will pop up.
Viewing and Editing Feedback Drafts
Run /feedback without any parameters to open the feedback queue.
This will list all unprocessed drafts from all your sessions, including those for which you closed the feedback card or never saw a card in the first place.
After selecting a draft, you can review it and perform the following operations:
Edit the title, category, and specific content;
Set Send transcript to yes or no. If the session record corresponding to when Claude created this draft still exists, this option defaults to yes, meaning the conversation segment will be submitted to Anthropic along with the feedback; choosing no sends only the feedback report itself;
Send the draft, delete the draft, or temporarily leave it in the queue to handle later.
If you want to manually write a feedback report yourself, press w to open the standard feedback window.
The /feedback command with text content, as well as the /bug command, will also directly open this standard feedback window.
Sending Feedback Drafts
When you send a draft, Claude Code submits it in the same way as a /feedback report, following the same data retention policies. After sending is complete, the draft is deleted from your local device.
If you send directly from a feedback card, it will show: ✓ Sent. If you send from the feedback queue, a receipt ID will be shown when the window closes.
Note that sending directly from a feedback card does not include the conversation transcript.
Claude Code saves your working directory information in the local draft to find the corresponding conversation transcript, but does not send this working directory.
For organizations with Zero Data Retention (ZDR) enabled, Claude Code does not provide this tool, and /feedback is similarly unavailable.
Deleting or Retaining Feedback Drafts
When you delete a draft, Claude Code simply removes it from your local device.
If you leave a draft in the feedback queue unprocessed, it will automatically expire after 30 days.
The feedback queue can save a maximum of 10 drafts across all sessions.
When Claude creates the 11th draft, Claude Code will automatically delete the earliest one.
Sessions Where Claude Cannot Automatically Draft Feedback
Claude Code only provides this feature in the following scenarios:
Interactive terminal sessions running on the user's own computer and directly using the Claude API, not through a cloud service provider.
The tool is not provided in the following scenarios:
- Non-interactive -p run modes, and Agent SDK sessions, as these scenarios lack an interface for reviewing the feedback queue;
- Cloud sessions, such as Claude Code on the web, because it cannot write feedback drafts to your local device;
Sessions run through the following platforms:
- Amazon Bedrock
- Claude Platform on AWS
- Google Cloud Agent Platform
- Microsoft Foundry
Sessions with the following environment variables or related configurations set:
- CLAUDE_CODE_SEND_FEEDBACK=0
- DISABLE_FEEDBACK_COMMAND=1
- Setting CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC to any non-empty value
- Feature-flag fetching is turned off;
- Organizations that have turned off product feedback functionality;
- Organizations with Zero Data Retention (ZDR) enabled.
This article is from the WeChat public account "Machine Heart"
