Docs
Concepts
Traces and replay
Read any run step by step and replay it against a new model.
4 min
Updated
A trace records every step of a run: prompts, tool calls, tokens, cost, latency and policy checks.
Reading a trace
Steps are drawn on a timeline. Guardrail steps are marked so you can see exactly where a run paused and who approved it.
Replay
Pick any run and replay it in a sandbox with a different model, prompt or tool version. Eventide diffs the outputs and flags steps that changed.
Replays never touch production systems. Tool calls are served from the recorded responses unless you allow live calls.