Activity types
| Type | Description |
|---|---|
activity | The parent working period contains verifications, fixes, and other events |
verification | A verification cycle run by the agent |
fix | A fix attempt made after a failed verification |
other | Tool calls and events that don’t belong to a verification or fix which are idle time, setup, general tool use |
Detail panels
Clicking an interval in the timeline opens a detail panel on the right. Each interval type has its own panel:Activity panel
Shows when you click an activity bar directly (without selecting a child):| Field | Description |
|---|---|
| Label | Activity 1, Activity 2, etc. |
| Duration | Total elapsed time for this activity |
| % of session | How much of the session this activity represents |
| Start / End | Absolute timestamps (End shows “in progress” if still running) |

Verification panel
Shows when you click a verification interval:- Status badge: passed, failed, or abandoned
- Video playback: browser session recording if available (space/K to play, arrows to seek, J/L for ±10s)
- Event timeline: every tool call and assertion in order, with timestamps, input/output sizes, and expandable JSON details
- Image artifacts: screenshots shown inline with lightbox

Fix panel
Shows when you click a fix interval:| Field | Description |
|---|---|
| Duration | Total fix time |
| Files | Unique files changed |
| Changes | Total file change events |
| Started | Absolute timestamp |
- fix_start: user and session that initiated the fix
- file_change: file path, operation (create / update / delete), lines added/removed, tool that made the change, and a View code button that opens a diff dialog showing the full changeset
- fix_end: total duration and reason the fix concluded

Other panel
Shows when you click an “other” interval, for events that occurred outside a named verification or fix:| Field | Description |
|---|---|
| Duration | Time span |
| Events | Count of events in this period |
| Activity | Which parent activity this belongs to |
| Started | Absolute timestamp |

Reading an activity
A healthy activity typically looks like:- Verification (passed) → task completes
- Verification (failed) → issues found
- Fix → agent corrects the code
- Verification (passed) → task completes