Feedback Bar
Status: built (2026-10-19), unverified by eye. HANDOFF.md written and ready-for-dev 2026-10-20.
Problem
Agent responses, suggestions and other agent output need a way for people to say whether it helped (thumbs up or down). Today each screen would build its own pair of buttons, with its own labels, pressed state and spacing. The same control belongs in several places: under an agent message in chat, in an accepted Suggestion Card, and under other agent output such as a Chain of Thought or a Code Diff.
Proposal
A small atomic component: a thumbs-up and thumbs-down pair with one piece of state, built from the local IconButton (its existing isPressed toggle, which maps to aria-pressed). Net-new (PDS has no feedback control). It is UI only: it reports the choice (up, down or none) and does nothing else. What the screen does with the signal (analytics, a reason flow, "thanks" text) is the screen's decision, and not decided yet.
An optional statusLabel replaces the thumbs with text (for example a thank-you) and is announced to screen readers. A children slot after the thumbs takes extra actions such as copy or retry.
Source
Screenshot of a thumbs pair under a response, shared by the designer (2026-10-19). A second screenshot, a bordered "Was this response helpful?" prompt bar with a dismiss button, was designed and then dropped: the designer does not need that design. What the signal is used for (quality tracking, evals, training) is not decided; this proposal provides the UI only.
Constraints
- Reuse first: the local
IconButton(pressed state), the localIcon. - No text hardcoded: every label is a prop, and the wording must not promise an outcome (for example training).
- Tokens only, light and dark, keyboard operable, visible focus. The two thumbs are a labelled group, each a toggle button.
Open questions
See decisions.md.