← All proposals

Context: AgentInbox

Net-new componentOpen in Storybook

proposals/AgentInbox/context.md22 lines · View on GitHub

Context: AgentInbox

Ideation sketch in Storybook, started 2026-11-17. Source: the designer's single-file reference prototype (a board of agent tasks), not ported.

Challenge

  • Does PDS already do this? No board, lanes or inbox in pds-toolkit-react beta.20. Closest: Panel and PanelList (expandable rows).
  • Could an existing component carry it? No. Lanes derived from status, state changes and a Board/List layout are their own behavior.
  • Composition or component? Mostly composed from PDS parts, with its own state and API: new component.
  • Who needs it? Not yet known (open).
  • Overlap with another proposal: reuses Event Log and Event Log Item for the steps (a dependency: the port needs them together) and the Spinner; may overlap Suggestion Card (Approve and Reject, kept as plain Buttons for now).
  • Cost: 4 statuses, 3 lanes, 2 layouts, open and closed cards, empty lanes, Figma component. Ripple: none, nothing imports it. Without it, a designer hand-composes PanelList rows under headings (list view only).
  • Verdict: new component (the designer's decision, 2026-11-17).

Need and scope

A board of background agent tasks in three lanes, with cards that open in place to show the last steps and the decisions. Board/List layout; narrow containers always get the list. Out for now: glide animation between lanes, filters, bulk actions, navigation to a task (left to onOpen).

Status

in-progress. Plan block not formally approved: the designer chose to ideate in Storybook, so gate 0 was passed on that basis.