tine replay

tine replay has three practical modes: inspect recorded steps, write a cached replay artifact, or rerun through an explicit harness.

Usage

tine replay <run_id_or_path> [--from-step <index_or_id_prefix>] [--mode cache|rerun]

Inspect Recorded Steps

--inspect and --dry-run do not create a new run.

tine replay finished.tine --inspect
tine replay finished.tine --from-step 5 --dry-run

Inspecting recorded steps...

  + 9e4b8c2a19dd done  "Planning research approach..."
  > 81bf0f67bb12 tool  search(query="solid-state battery 2026")
  + 6d4a0b270a5f done  "Synthesizing findings..."

Cached Replay

--mode cache forks from the selected tip and records replay metadata showing how many steps were reused.

tine replay finished.tine --mode cache --save replayed.tine

Harness Rerun

--mode rerun requires --harness from the CLI. The selected harness gets recorded context and produces a new run graph.

tine replay finished.tine \
  --mode rerun \
  --harness codex \
  --prompt "Rerun this task using the recorded context." \
  --save replayed_codex.tine \
  --compare

Options

• --from-step selects a traversal index, full ID, or unique ID prefix.
• --save writes the replayed run to a specific path.
• --compare prints a diff after harness replay.
• --harness accepts the same harness names as tine run.