Skip to main content
A trace is one attempt by one model at one task. It records the whole conversation, every tool call and its result, what the environment showed, the grade, and the cost. Open a trace from a job’s Traces tab, a task’s Traces tab, or a result in the taskset grid.

Read the conversation

The conversation shows the prompt, the model’s messages, and each tool call with its result. It ends with the Evaluation result: the reward and, for rubric grading, the judge model, a Judge summary, and every criterion with its weight, whether it was met, and the judge’s reason. Copy JSON copies the raw result. The score at the top of the conversation jumps to it. The reward is the verdict, not the explanation. Read the steps and the grading together to tell whether the agent solved the task or found a shortcut; QA agents do this reading for you at scale. The header shows who ran the trace, its job, its reward, whether it is public, and LIVE while it runs. When a trace stopped early, a badge says why: An execution badge says where the trace ran, which decides what HUD bills:

Inspect a trace

Open inspector shows the trace’s views beside the conversation. Which views appear depends on what the environment recorded: Invalidating a trace keeps it out of leaderboards and reward summaries. See keep bad traces out of the score.

Share a trace

The More trace actions menu has Compact view, which collapses sections of the conversation, Copy conversation, and, for editors, Share trace. Share invites people or teams as Viewer or Editor, or makes the trace public so anyone with the link can view it. Public viewers see the conversation and the Screen, Robotics, and Workspace views. They also see your team’s QA verdicts, summaries, and findings, without the evidence behind them. Source, Logs, Term, Debug, and Info stay private.