RunSummaryCard

Markdown

What a run did, for reading afterwards: the goal, the outcome, what it changed and what was left undone.

Use it for
What a run did, read afterwards, with what it changed.
Not for
Live progress. Try AgentSteps.

RunSummaryCard preview

Loading example…

Installation

npm install @stackunseen/ui
import { RunSummaryCard } from '@stackunseen/ui/conversation-flow';
Styles: @stackunseen/ui/styles.css and @stackunseen/ui/conversation-flow.css

Usage and props

Import this component from @stackunseen/ui/conversation-flow. Load @stackunseen/ui/styles.css first, then @stackunseen/ui/conversation-flow.css.

A change counts as done only when your server has confirmed it. Outcomes you don’t know are shown as unknown, not hidden. Time and cost say how they were measured.

Supported inputs

This is the public signature used by this example. Open Code to see how the values and callbacks fit together.

summary: RunSummary · receipts? · onOpenEffect? · actions?
How state and callbacks work
All props

Loading…

For your coding agent

Give the agent this page instead of a screenshot. The prompt wraps the page with the install and import lines and the rule that your server, not a click, completes an action.

Contract
summary: RunSummary · receipts? · onOpenEffect? · actions?
Keeps honest
A change counts as done only when your server has confirmed it. Outcomes you don’t know are shown as unknown, not hidden. Time and cost say how they were measured.
MCP
read_component "RunSummaryCard" on the docs endpoint
Open the Markdown file

Keyboard and customization

Keyboard

Tab reaches controls; Enter or Space activates buttons. Accordions use arrow keys, Home and End. Select menus support arrows and typeahead; Escape closes menus and dialogs and restores focus.

Customization

Change shared colors, spacing, corners and icons with the theme. Use the component's supported props to adapt its content and layout. Customization guide and Theme Studio