Skip to main content
A Trace is the record of a single Flow run. It captures the prompts each Agent received and the outputs it produced, tool calls, and handoffs between Agents as spans, along with duration, tokens, and cost. Open Traces in the sidebar to see every run in the workspace.

When to look at traces

  • A user reports a bad answer
  • You want to verify that an answer stands on real evidence
  • You are hunting for a run with unusual cost or duration
  • You deployed a new version and want to skim its runs

What a trace holds

Click a row to open the detail panel. The left side has the span tree (Trace), Verification, and Feedback sections; the right side shows the span you select. See Inspect a run for the full layout.

Verification and signals

Run Verification on a trace to break the answer into claims, check them against evidence, and record a verdict on the trace. Claims without support are registered as signals and feed the improvement loop. See Verification & verdicts.

Learn more

Inspect a run

Walk the span tree: prompts, tool calls, handoffs.

Tool calls

What each tool was called with and what came back.

Verification & verdicts

Verify answers claim by claim and record verdicts.

Cost & latency

Duration, tokens, and cost recorded per run.

Feedback

Leave ratings and corrections right on the trace.

Search & filter

Status tabs, full-text search, flow, verdict, and date filters.