claude-code - 💡(How to fix) Fix Number keys collide between in-message numbered options and feedback shortcuts [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#53310Fetched 2026-04-26 05:19:00
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Problem

Several skills and prompts (e.g. the Superpowers brainstorming/plan flows) present numbered choices in Claude's response — "Reply 1 to do X, 2 to do Y, 3 to do Z."

When Claude Code asks for feedback on a response, the feedback prompt also uses number keys (1 = bad, 2 = good, etc.). If I press 1 intending to pick option 1 from Claude's message, it gets captured by the feedback prompt and sent as negative feedback on the response I was actually trying to act on.

This happens often enough to be a real annoyance, and it actively poisons the feedback signal — Anthropic is receiving "bad" ratings that are really "I wanted option 1."

Suggestions

A few possible fixes (any one would help):

  1. Don't bind bare number keys to feedback ratings — require a modifier or a dedicated keystroke to enter feedback mode first.
  2. Only show the feedback prompt when explicitly invoked, not as the default post-turn input state.
  3. Make the feedback prompt visually distinct enough that it's obvious when number keys will be captured by it vs. sent as a message.
  4. Treat number keys as message input by default and only route to feedback when the user is clearly in the feedback UI.

Impact

  • User frustration (sent the wrong thing, can't easily un-send)
  • Polluted feedback data on Anthropic's side

extent analysis

TL;DR

Modify the feedback prompt to require a modifier or dedicated keystroke to prevent unintended capture of number keys.

Guidance

  • Consider implementing a modifier key (e.g., Ctrl or Alt) to activate feedback mode, ensuring number keys are not bound to feedback ratings by default.
  • Visually distinguish the feedback prompt to clearly indicate when number keys will be captured, reducing user confusion.
  • Evaluate the current feedback prompt invocation logic to determine if it can be improved to only appear when explicitly requested.
  • Assess the feasibility of treating number keys as message input by default, routing to feedback only when the user is clearly in the feedback UI.

Example

No code snippet is provided as the issue does not imply a specific programming context.

Notes

The suggested modifications aim to address the issue without requiring significant changes to the existing system. However, the effectiveness of these solutions may depend on the specific implementation details of the feedback prompt and input handling mechanisms.

Recommendation

Apply workaround: Modify the feedback prompt to require a modifier or dedicated keystroke, as this approach directly addresses the root cause of the issue and can be implemented without waiting for a potential fix in a future version.

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

claude-code - 💡(How to fix) Fix Number keys collide between in-message numbered options and feedback shortcuts [1 participants]