SendFeedback confirms a draft was queued, but /feedback panel shows "No feedback drafts queued"

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 14, 2026

What happened

Claude used its internal SendFeedback tool during a session, which returned a confirmation that a feedback draft was "queued locally (max 10 kept)" and that it could be reviewed and sent via /feedback. Running /feedback immediately afterward showed:

Feedback drafts

  No feedback drafts queued.

  Claude drafts feedback at high-signal moments; drafts appear here for your review.

   > + Write new feedback

  /bug works anytime. Any other key closes this panel.

  Enter to write new feedback · Esc to close

This happened twice in the same session, with two separate SendFeedback calls each returning a "queued locally" confirmation, and both subsequent /feedback invocations showing zero drafts.

Repro steps

  1. In a session where Claude calls its internal SendFeedback tool (or trigger one via a natural high-signal moment), note the "queued locally" confirmation.
  2. Immediately run /feedback in the same session.

Expected

The /feedback panel shows the queued draft(s) for review, matching the tool's confirmation.

Actual

The panel shows "No feedback drafts queued," with no way to review or send the draft the tool said it queued.

View original on GitHub ↗