Claude Code lets Claude draft its own bug reports
Filing feedback about a Claude Code problem has always meant noticing the problem, remembering to run /bug, and writing up what happened yourself. Version 2.1.247 (August 26, 2026) adds the SendFeedback tool, so Claude can start that report instead of you.
Claude queues a draft with SendFeedback when:
- A tool or command keeps failing
- It can't help with something you asked for
- You point out a mistake it made, or it notices one
- You ask it to file feedback
Nothing reaches Anthropic until you send it. Claude Code saves each draft on your machine under ~/.claude/feedback/drafts/. After Claude queues one, a card appears above your prompt with the draft's title: press 1 to review it, 2 twice to send it as written, or 0 to dismiss it — a dismissed draft stays in the queue. Run /feedback with no argument to open the full queue, listing every draft across your sessions, including ones you never saw a card for. From there you can edit the title, area, and details, and choose whether the report includes the session transcript.
By default you see at most three cards per session before Claude Code switches to showing only a queued-draft count in the prompt footer. The feedbackDrafts setting controls the behavior directly:
{
"feedbackDrafts": "quiet"
}
"notify"— the default: shows a card for each queued draft, up to the per-session limit"quiet"— drafts queue silently; you see a count in the footer and review them in/feedback"off"— removes theSendFeedbacktool entirely, so Claude can't queue drafts
feedbackDrafts is a user or managed setting only — Claude Code ignores it in project and local settings files, so a repo can't turn this on or off for itself.
What this means
The friction this removes is the part where you have to notice and remember to report — the send step, and what gets included, is still entirely yours. See the Claude Code sheet for the full settings surface.