Stats
Four metrics shown at the top of the panel:| Field | Description |
|---|---|
| Duration | Total elapsed time for this interval |
| Events | Number of tool call events recorded |
| Activity | Which parent activity this interval belongs to (e.g., Activity 1) |
| Started | Absolute timestamp when the interval began |
Event timeline
A chronological list of every tool call and agentic event in the interval. Each row shows:- Tool name: the tool invoked, with any prefix stripped for readability
- MCP server: if the tool belongs to an MCP server, the server name is shown as a chip
- Tool type:
mcp,skill, orsub_agentwhere applicable - Time offset: relative to the start of the interval (e.g.,
+4s 210ms) - Absolute timestamp
- Duration: how long the tool call took
- Input size: bytes of input passed to the tool
- Response size: bytes returned by the tool
- Error: error message if the call failed
- View input: button opens the full tool input as JSON
| Color | Domain |
|---|---|
| Blue | File operations (read, write, edit) |
| Purple | Search |
| Orange | Shell / exec (Bash, terminal) |
| Green | Web (fetch, browser) |
| Pink | UI interactions |
| Gray | Diagnostic / flow control |
What you’ll typically see here
Other intervals contain the bulk of an agent’s day-to-day work, the parts that aren’t about proving a change is correct:- Reading and exploring: file reads, directory listings, grep searches
- Planning and reasoning: turns where the agent thinks without calling tools, or uses TodoWrite / task tracking
- Web activity: WebFetch, WebSearch, or MCP-based HTTP calls made during research
- Shell commands: Bash invocations for building, running tests, installing dependencies
- Sub-agent interactions: spawning and waiting on background agents
- MCP tool calls: any tool from a connected MCP server not tied to a verification cycle