Replays re-execute a sealed session — exactly, guided, or partial. See replay concepts for modes.Documentation Index
Fetch the complete documentation index at: https://docs.nusomi.com/llms.txt
Use this file to discover all available pages before exploring further.
Trigger a replay
Body
| Field | Required | Notes |
|---|---|---|
session_id | yes | Source session. Must be sealed. |
mode | yes | exact | guided | partial. |
from_frame | only for partial | Frame id. |
from_tag | optional | Use a tag as the anchor instead of from_frame. |
model | only for guided | Defaults to workspace setting. |
budget_ms | optional | Wall-clock cap. Default 5 min. |
sandbox | optional | dry (default) | live | staging:<env>. |
metadata | optional | Free-form JSON, surfaced on the replay session. |
Response 202
Get a replay
status progresses queued → running → completed | diverged | failed | budget_exceeded.
Replay session
Oncereplay_session_id is set, that session can be queried like any other (events, frames, exports). Use it to verify the replay matched the original.
Stream replay progress
step events as the replay progresses, plus a final result event with the outcome.
Cancel a replay
cancelled. Live-sandbox cancels make a best-effort to stop external side effects but cannot guarantee atomicity (e.g. a network request already in flight).
List replays
limit / cursor pagination.
Recovery
Recovery is a thin wrapper that finds the rightfrom_frame for you and triggers a partial guided replay:
/v1/replays.