RunBoard

Markdown

All your runs on one board, grouped by what they need, with live clocks, the newest steps, filters and actions.

Use it for
Many runs across threads, grouped by what they need.
Not for
One run in detail. Try RunInspector or RunSummaryCard.

RunBoard preview

Loading example…

Installation

npm install @stackunseen/ui
import { RunBoard } 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.

Status, times and heartbeats come from your server. A run that has gone quiet is flagged, never assumed finished. An action counts as done only once your server confirms it.

Supported inputs

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

runs: RunCard[] (steps?, model?, startedAt?, cost?) · filter? · onFilterChange? · selectedId? · onSelect? · onAction? · receipts? · staleAfterMs? · now? · label? · renderCardTrailing?
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
runs: RunCard[] (steps?, model?, startedAt?, cost?) · filter? · onFilterChange? · selectedId? · onSelect? · onAction? · receipts? · staleAfterMs? · now? · label? · renderCardTrailing?
Keeps honest
Status, times and heartbeats come from your server. A run that has gone quiet is flagged, never assumed finished. An action counts as done only once your server confirms it.
MCP
read_component "RunBoard" on the docs endpoint
Open the Markdown file

Keyboard and customization

Keyboard

Arrow keys move between cards and columns; Home and End jump within a column; Enter opens a run.

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