Reading an agent trace

An eval run records the full agent session as a turn-by-turn trace. Read it with get_trace; pull run-level context first with get_report so you know the metrics, the key finding, the prompt, and which provider was under test.

Tools

• get_trace({ slug, offset?, limit?, includeBrowser? }) — the parsed conversation log for a report.
  • Default returns the last 20 turns (offset defaults to totalTurns - limit). To read from the start, pass offset: 0. Page forward with offset/limit.
  • includeBrowser: true interleaves the browser-agent screenshots (with each shot's thinking/action/page URL) in timestamp order. Omit it when you only care about the code agent (see the reading-browser-screenshots skill for how to analyze them, and note the dashboard's #turn-N anchors assume screenshots are merged in).
  • Returns: { slug, totalTurns, showing:{offset,limit,count}, totalToolCalls, totalErrors, totalInterruptions, toolCounts, turns[], setupCommand, healthcheckLog }. toolCounts is a per-tool call histogram — scan it first to see where the agent spent its effort.
  • setupCommand is the bash script that ran before the agent, and healthcheckLog is that script's own output. When a run failed early or the agent started from a broken environment, read the log first — the cause is usually there, not in the turns.
• get_report({ slug }) — for the surrounding context (metrics, legacy.keyFinding, summary, recommendations, the prompt).

The turn model

Each turn has type, content[] (ContentBlock array), hasError, toolNames[], and timing (timestamp, durationMs or gapAfterMs).