PDS proposals
← All proposals

Suggestion Card

A card for use inside an agent `ChatMessage`:

Net-new componentOpen in Storybook

proposals/SuggestionCard/context.md25 lines · View on GitHub

Suggestion Card

Problem

When an agent proposes changes in a chat (for example edits to page copy), the user needs to see exactly what would change and decide: accept, ask for a different change, or dismiss. PDS has no component for an agent's proposal in a conversation. This is a net-new pattern.

Proposal

A card for use inside an agent ChatMessage:

  • a title ("2 changes") and a short description,
  • a list of changes, each a field name with BEFORE and AFTER values (SuggestionChange),
  • an actions slot for the decision buttons (in the reference: Accept, Refine, Dismiss),
  • two states: pending (actions shown) and accepted (the actions are replaced by a result line, so the card in the history can't be accepted twice).

Not a variant of the agentic panel in the same design set: that one is a full-width report on a page (Panel with agentic border); this one is a decision prompt in the message stream.

Out of scope for now

Dismissed and expired states, what Refine does, the accepted state's final design ("we can refine that later"), a height cap or scroll for many changes, and code-diff changes (the panel's file diff).

Source

Erika's screenshot (~/Desktop/Screenshot 2026-10-13 at 12.33.23 PM.png): "2 changes" card with Eyebrow and Description before/after rows, and Accept / Refine / Dismiss. No Figma or Jira links.