Feedback rating prompt collides with assistant's numbered questions in the same input context

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Description:

Claude Code occasionally shows a feedback prompt like "1-Bad, 2-OK, 3-Good" (or similar rating scale) in the main chat input. Meanwhile, the
assistant frequently asks numbered questions in its replies — e.g., "1. Do X? 2. Should we Y? 3. Do Z?" — and expects short numeric answers like
"1" or "1, 3".

Because both flows consume single-digit input in the same place, a user intending to answer question #1 from the assistant can instead submit a
"1 = Bad" rating. The feedback gets recorded incorrectly, and the intended answer never reaches the assistant.

Reproduction:

1. Have the assistant ask 2–3 numbered questions in a single message.
2. Shortly after, a feedback rating prompt appears in the input.
3. Type "1" (or any single digit) intending to answer question #1.
4. Claude Code captures it as a feedback rating.

Impact:

• Low-signal telemetry (users rate "Bad" without meaning to).
• Lost intent in the conversation (assistant never sees the intended answer).
• Frustration — happened to me at least twice so far.

Suggestions (any one would help):

• Show the feedback prompt in a modal / separate UI surface, not in the same input that accepts chat.
• Require an explicit verb or prefix for feedback (e.g., /rate 1).
• Defer feedback until a pause in active conversation (idle timeout).
• Make it obvious in the input when a digit will go to feedback vs to the chat (distinct styling / border color / placeholder text).

Proposed Solution

Make feedback rating options clickable buttons instead of accepting numeric input via the chat input field.

• Render the rating scale (e.g., "Bad / OK / Good" or 1–5) as a row of clickable buttons in a dedicated UI surface (inline panel, modal, or a

fixed feedback bar), separate from the chat input.

• Clicking a button submits the rating directly; the chat input stays exclusively for conversation.
• This eliminates any ambiguity between "digit I type = feedback rating" and "digit I type = answer to assistant's numbered question". The two

input surfaces are physically separate, and accidental miss-rating becomes structurally impossible.

Optionally, a small "Skip" or "Dismiss" action on the same panel for users who don't want to rate — so closing it doesn't require typing
anything into the chat input.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_