[FEATURE] Replace session-feedback toast with per-turn reaction affordance + inline text feedback

Preflight Checklist

• [x] I have searched existing requests
• [x] This is a single feature request

Problem Statement

The Claude Code VS Code extension shows a toast asking "How is Claude doing this session?" with 3 fixed-rating options and no affordance for further detail. The toast is dismissable but doesn't auto-dismiss — it sits until the user takes action, which creates real friction:

• It occasionally covers conversation/editor content the user is trying to read, and being visually loud (presumably by design — they want it seen), it's hard to look past while it's there.
• The 3-option shape collapses a multi-dimensional read (was the output good? the latency? the tone? a specific turn?) into one undifferentiated score per session.
• There's no path to attach a specific turn or detail, so a rating signals dissatisfaction without telling Anthropic what went wrong.
• Sessions are long and multi-shaped — "how is Claude doing this session" averaged over many turns is closer to noise than signal, and the user knows it, which depresses response quality further.

The pattern reads as a junior solution to the "we need user feedback" problem — a well-meaning UX research instinct shipped before the form-factor was right.

Related existing issues capture facets of this: #61281 (rating prompt collides with active work, leaves no transcript record), #66356 (sentiment that the question is meaningless), #68085 (grammatical mismatch on the answers). This request proposes a structural reframe rather than another button on the same toast.

Proposed Solution

Replace the session-end toast with per-turn affordances, modeled on standard chat platforms (Slack, Discord, Linear comments):

1. Emoji reactions on every assistant turn. A small reaction picker at the end of each response. 👍 / 👎 as defaults; richer set (🎯 on-target, 🤔 confusing, 🐛 buggy, 🪄 surprisingly good, ⏱️ too slow, etc.) optional. Aggregated across users, this gives Anthropic deep, dimensional signal — turn-level, not session-level — without disrupting flow.
2. Inline "report this turn" affordance — a small button on each turn that opens a free-text field, pre-attached to the specific turn's context. For when a turn goes sideways and the user wants to say why in their own words.

Why this is better than the current toast

• Non-disruptive. Reactions sit in-place; user opts in when they have a read. Toast forces an interaction and visually blocks content until dismissed.
• Higher-resolution signal. Per-turn ratings reveal which turn (slow tool call, wrong code, great explanation) rather than averaging over 50 turns.
• Expressive. Emoji vocabulary captures gradients (delight, surprise, confusion, frustration) that 3-option rating buttons collapse.
• Familiar. Every modern chat platform has this; users already know the gesture.
• Open-ended path for detail when it matters. Inline text on the specific turn, with context auto-attached.

Alternative Solutions

• Make the toast auto-dismiss after N seconds (lower-friction status quo, doesn't fix the signal-quality problem).
• Add a "write more" 4th option to the toast (#63443's proposal). Helps the privacy concern there but doesn't address the disruption or the session-averaging problems.

Priority

Medium — current toast is producing weak signal at a real flow cost; the reframe is a structural improvement.

Feature Category

UI / Feedback

Additional Context

Feedback from a heavy daily Claude Code user (VS Code extension). The signal-vs-friction tradeoff inverts cleanly with per-turn reactions: lower friction, higher signal, familiar gesture.