claude-code - 💡(How to fix) Fix [Bug] Single digit input misinterpreted as feedback instead of chat message [2 comments, 2 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#50854Fetched 2026-04-20 12:11:13
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×3commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

Bug Description Claude provided 3 options to me numbered 1 through 3. I typed 1 and instead of being accepted as chat input, it was treated as feedback on Claude's response to me (bad). It was a great response and I wouldn't want your training feedback to be a false negative. Maybe you can improve the way edge cases like this are handled?

Environment Info

  • Platform: darwin
  • Terminal: ssh-session
  • Version: 2.1.114
  • Feedback ID: 0ff33c7b-d57e-4973-a6f0-f531d7d2c9ac

extent analysis

TL;DR

The issue may be resolved by improving the input handling to distinguish between chat input and feedback on Claude's responses.

Guidance

  • Review the current input handling logic to identify why the typed "1" was treated as feedback instead of chat input.
  • Consider adding a mechanism to explicitly indicate when a user is providing feedback versus chat input, such as a specific command or prefix.
  • Investigate if there are any existing configurations or settings that can be adjusted to handle such edge cases.
  • Verify if this issue is specific to the current version (2.1.114) or if it persists across different versions.

Notes

The provided information does not include detailed technical specifications of the input handling mechanism, so a more precise solution cannot be offered without further details.

Recommendation

Apply workaround: Improve input handling logic to handle edge cases like this, as the current version (2.1.114) may not have a built-in fix for this specific issue.

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