PDS proposals
← All proposals

Event log with agent

A recipe, not a component: a story and Usage page that compose existing proposals.

Extends a PDS componentOpen in Storybook

proposals/EventLogWithAgent/context.md33 lines · View on GitHub

Event log with agent

Problem

An agent usually joins a log that already has events in it (deploys, checks, approvals), works for a while, then hands back. Screens need to show where the agent started and stopped and which entries are the agent's, without a special component for the region.

Proposal

A recipe, not a component: a story and Usage page that compose existing proposals.

  • Timeline with hasRail holds the whole log.
  • Neutral TimelineItems before the agent joins.
  • An agentic LabeledDivider ("Zappy engaged") opens the region.
  • isAgentic TimelineItems, a ChainOfThought and a live ThinkingState are the agent's entries.
  • A second agentic LabeledDivider closes the region when the agent hands back.

It adds no props, classes or tokens. Where the region starts and stops, what the dividers say and which entries are agentic are screen decisions.

Source

Erika's screenshots (2026-10-16) of a deploy log with a "Zappy engaged" divider and an agent sandbox investigation. See ../Timeline/context.md.

Constraints

  • Uses only existing proposals: Timeline, TimelineItem, LabeledDivider, ChainOfThought, ThinkingState. Both dividers use size='xs' and tone='agentic' (the gradient; the purple agentic-filled was removed 2026-10-21).
  • All sample text lives in the story, not in the components.
  • Light and dark; keyboard operable (the expandable rows and the Chain of Thought summary).

Open questions

  • The dividers use the gradient agentic tone, the one the Labeled Divider component keeps (the purple agentic-filled was removed on 2026-10-21).
  • Does the region need a tint or bracket between the dividers, or are the dividers plus isAgentic enough? The recipe ships with the dividers plus isAgentic.