The steps of a run with status and duration: missions, agent tool calls, rollouts, CI runs, audit trails. Steps open to show input, output or sub-steps; an optional waterfall bar.
- Load site maphall-b-v12, Done420 ms
- Plan routeplanner, Done1.3 s
- Drive to door 3nav, Running
- Take photo, Waiting
- Return to dock, Waiting
Trace default
Install
npx shadcn add @syncrobotic/trace Also installs: lucide-react, radix-ui, @syncrobotic/cn, @syncrobotic/spinner
Overview
The steps of a run in order, each with a status and a duration, that open to show input, output and sub-steps.
When to use
- What a robot did on a mission.
- An AI agent's tool calls and reasoning.
- Firmware rollouts, map builds and other CI-like runs.
- Audit trails of who changed what.
More examples
States and real uses. Each example is also a Storybook story and a visual regression test.
- Load site map, Done420 ms
- Plan route, Done1.3 s
- Drive to door 3, FailedPath blocked by a pallet at corridor B-4 for 30 s.34 s
- Take photo, Skipped
- Return to dock, Done52 s
Trace failed step
Trace expandable
- Night patrol · South, Running
Trace nested
- search_events{ site: "hall-b", since: "22:00" }, Done180 ms
- get_snapshot{ robot: "7F3A", camera: "front" }, Done940 ms
- create_work_order{ door: "B", priority: "normal" }, Running
Trace agent tool calls
- Authenticate, Done120 ms
- Fetch fleet, Done680 ms
- Fetch maps, Done1.8 s
- Fetch cameras, Warning2 of 14 slow2.9 s
- Render, Done500 ms
Trace waterfall
Firmware 2.4.1 rollout, Warning32 m 00 s5 done1 warning
- Robot 7F3A2.4.0 → 2.4.1, Done5 m 22 s
- Robot DAA62.4.0 → 2.4.1, Done5 m 27 s
- Robot 9E372.4.0 → 2.4.1, Done5 m 23 s
- Robot 17152.4.0 → 2.4.1, Done5 m 20 s
- Robot B54C2.4.0 → 2.4.1, Done5 m 26 s
- Robot 53842.4.0 → 2.4.1, WarningUpdated, but the lidar self-test took twice as long.6 m 24 s
Trace with header
- Boot, Done1.8 s
- Self-test, Done4.2 s
- Localize, Done2.6 s
- Load mission, Done300 ms
- Arm, Done120 ms
Trace dense
- Map editedlin@site, DoneZone C marked no-go.09:41
- Route publishedlin@site, Done09:44
- Retention changedadmin, WarningCamera clips kept 7 days instead of 30.10:02
Trace audit log
- Waiting, Waiting
- Running, Running
- Done, Done1.2 s
- Warning, Warning2.4 s
- Failed, Failed800 ms
- Skipped, Skipped
Trace all statuses
Map build #312, Failed1 m 36 s3 done1 failed1 skipped
- Checkout, Done4.0 s
- Merge scans, Done38 s
- Build occupancy grid, Done41 s
- Publish, Skipped
Trace ci
- Charge to 80 %, Done1 h 04 m
- Full map scan, Done2 h 01 m
- Ping, Done12 ms
Trace long durations
Usage rules
- Done steps are a neutral check; only warnings and failures are coloured.
- A failed step says why in its description; the raw error goes in a TraceCode inside it.
- Open the step that needs attention by default, nothing else.
- total plus start and duration draw the waterfall; leave them out for a plain list.
Changelog
- 0.27.02026-11-21A span with nothing under it opens and closes in place instead of as tall as its parent span.
- 0.23.02026-11-20Every word it says can be translated without editing the source: Trace (inherited by nested traces) and TraceHeader take
labels: the six status words, the counts and how durations are written. - 0.17.32026-11-19Tracks and quiet shapes use the new --track token, so they read in dark mode (1.5:1 on their surface; they were near invisible).