What Replay is#
Replay is the post-hoc audit surface for a job. While Agents shows what's happening live, Replay shows what did happen — the governed chain correlating a builder job with every delivery step, runtime session, and evidence record it produced.
Open at /dashboard/<workspaceId>/observe/replays to see the latest replay chain for the workspace (/dashboard/<workspaceId>/observe/replays/<replayId> for one in depth).
What's in a replay chain#
| Layer | What it shows |
|---|---|
| Job | The intent that started the work |
| Delivery | The plan, dispatch, and orchestration that turned intent into action |
| Runtime | The sessions that actually ran — model calls, tool calls, results |
| Evidence | The artifacts and approvals produced along the way |
Together these form a single chain you can step through, share, or export.
Empty state#
A workspace with no jobs yet shows an empty state. Replay populates as soon as a builder job has a correlated delivery, runtime, or evidence chain — usually after the first real Sidekick run.
Replay vs Evidence Vault#
Evidence Vault is the full searchable archive across all jobs. Replay is the focused, time-ordered view of a single chain. Use Evidence Vault to find something; use Replay to follow what happened end-to-end.
Governance#
Every receipt in the replay chain is hash-chained and tamper-evident. Receipts written since receipt signing was enabled also carry an Ed25519 signature that an auditor can verify with the signing public key; older receipts remain hash-chained but unsigned — see Traces and evidence for the underlying contract. Members and above can view; export and download are role-gated.
Sidekick's autonomy policy determines what writes are recorded — every gated approval, budget check, and tool-call decision lands in the chain.