claude-code - 💡(How to fix) Fix [BUG] Feedback is too easy to mis-apply [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47982Fetched 2026-04-15 06:36:46
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Participants
Timeline (top)
labeled ×4unlabeled ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When claude asks for feedback on a 1-5 scale, it uses the next input character as input. I often am using lists with claude code, and will type 1, as in the first thing it should do. This is interpreted as feedback. You are likely getting a lot of bad feedback data due to this. I suggest having the user confirm or do something to enter feedback, not just grabbing the next thing they type. The feedback prompt is extremely easy to overlook.

What Should Happen?

The "1" I type should be accepted as normal input, not feedback.

Error Messages/Logs

Steps to Reproduce

  1. Use claude until the feedback prompt appears
  2. Type "1" as if you are about to try and give claude a list of items
  3. Your "1" is now interpreted as feedback.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.107 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

Modify the feedback prompt to require explicit user confirmation to prevent misinterpreting subsequent input as feedback.

Guidance

  • Consider adding a confirmation step after the feedback prompt, such as "Press Enter to submit feedback" or "Type 'submit' to confirm your rating".
  • Update the feedback prompt to clearly indicate that the next input will be interpreted as feedback, reducing the likelihood of user error.
  • Explore using a more explicit input method for feedback, such as a separate command or a pop-up dialog, to minimize conflicts with normal user input.
  • Review existing user feedback data to identify and potentially correct any inaccurate or misleading feedback caused by this issue.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a design or interaction change.

Notes

The solution may require adjustments to the Claude Code's user interface or interaction design, which could involve changes to the underlying code or configuration. The exact implementation details are not specified in the issue.

Recommendation

Apply a workaround, such as adding a confirmation step to the feedback prompt, to mitigate the issue until a more permanent solution can be implemented. This will help prevent further collection of inaccurate feedback data.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING