Review run activity, graph, errors, trace, and usage
Run sessions use tabs to separate the conversation from supporting evidence. Chat, Graph, Diff, and Errors are always available. PR appears after the run has a pull request, and Trace appears when the run has an OpenTelemetry trace ID.
Chat
Chat is the chronological session timeline. It shows your messages, agent replies, grouped activity, questions and approvals, pending input, and live working state. See Chat with an agent.
Graph
Graph visualizes delegated and sub-agent work. Use it to see parallel tasks, dependencies, and the status of child work. It is most useful when a run delegates research, implementation, testing, or review.
Diff
Diff shows repository changes and any available new files. If the run has multiple workspace repositories, select the repository before reviewing changes. A live diff can change while the run is active, and large diffs or new-file lists can be truncated.
PR
PR lists pull requests associated with the run, including checks and review threads. You can refresh the panel and, when you can send messages, select unresolved review threads and use Send to agent to create a focused follow-up.
Errors
Errors keeps recovered and terminal run errors visible after retries. It can include errors reported by the worker pod, run status, or activity. It intentionally excludes routine pod output and trace data. The tab retains the 200 most recent errors.
Use Errors for a concise failure history; use Trace when you need span-level timing and telemetry.
Trace
Trace displays OpenTelemetry spans when the run emits tracing data. It includes a waterfall view and, when available, usage summaries and task breakdowns for top-level work and subagents. A trace can be unavailable or contain no spans even when the run has activity.
The Trace tab is not Meta-Harness capture. Meta-Harness is an operator-controlled archive for platform self-development; see Meta-Harness trace capture.
Usage and context
The session can show run cost and context-window usage. The Trace tab can also show recorded input and output tokens, tool usage, and task-level usage when that data is available.
High context usage means the agent is carrying substantial history. If the next step does not need that detail, ask for a compact handoff:
Before continuing, summarize the current state, files changed, tests run, decisions made, and remaining risks in 10 bullets.