An activity is a discrete action recorded within a session. Activities form the chronological record of everything the agent did — what files it changed, when it verified, how it responded to failures.Documentation Index
Fetch the complete documentation index at: https://docs.ironbee.ai/llms.txt
Use this file to discover all available pages before exploring further.
Activity types
| Type | Description |
|---|---|
code_change | The agent edits one or more source files |
verification | The agent runs a browser, Node, or backend verification cycle |
fix | The agent makes corrections after a failed verification |
tool_call | A single devtools invocation (navigation, screenshot, probe, etc.) |
Activities list
The activities tab on a session detail page shows all activities in chronological order. Each row includes:- Type — icon indicating the activity category
- Timestamp — when the activity started
- Duration — how long the activity took
- Summary — a brief description (files changed, pages tested, tools used)
- Outcome — pass / fail / n/a depending on type
Activity detail
Clicking an activity opens its detail view, which varies by type:Code change detail
- List of files modified with diff sizes
- Whether the change triggered a verification requirement
- Which verification cycle was activated (browser / node / backend)
Verification detail
Fix detail
- See Fix Detail
Tool call detail
- Tool name and input arguments
- Response summary
- Timing within the parent activity
Reading the activity log
Activities tell a story. A healthy session typically looks like:- Code change → files edited
- Verification (passed) → task completes
- Code change → files edited
- Verification (failed) → console errors found
- Fix → agent corrects the issue
- Verification (passed) → task completes