Runs

Every run is kept: its reports, screenshots, and the complete conversation. The Runs page is where you open them.

Open a run's results

1. Open the Runs page.
2. Pick the run in the sidebar, newest first, one entry per run with its pass tally.
3. Choose what to look at:
   • Conversation log: the full execution record (below).
   • Summary report: the run-level table, one row per test.
   • The per-test entries: each test's test report with its status badge.

Open in Explorer on a test jumps to its files on disk, the run's folder is one level up.

Conversation log

Beside the written reports, every run keeps its full conversation, each agent message, tool call, and screenshot in order. Where the report gives the result, the log is the complete execution record: open it when a status alone doesn't explain what happened.

Reading it element by element:

• Numbered circle + TEST header: one phase (setup, a test case, teardown) with its file path, status badge (PASS/FAIL), and how many tool calls it took, this is where you see each test.
• Text lines: the agent's narration, what it sees on screen and what it decides to do next.
• Chips: tool calls, a screenshot, a keystroke, a click, or a named tool like Save screenshot / Write file, with the result behind it.
• 350 → 26: tokens in → out for that step, the cost signal of the run.
• 500ms: the step's latency.

During a run the same view streams live, Watch it live.

Share results

To hand a result to a developer or attach it to a ticket, zip the run's timestamped folder (Open in Explorer on a test, one level up), the reports are plain Markdown with the step screenshots next to them, readable anywhere.

On disk

Each run is one timestamped folder under agent_workspace/:

<project>/agent_workspace/
└── 2026-07-23_21-56-55/          ← one folder per run
    ├── conversation.json          ← the conversation (the app re-renders it)
    ├── summary_report.md          ← run-level table
    └── open_notepad_windows/      ← one folder per test
        ├── open_notepad_windows_report.md   ← the test report
        ├── step_1.png
        └── step_2.png

Run folders are independent of each other, archive or delete old ones as your evidence-retention policy requires; the Runs list and Dashboard reflect whatever folders exist. The folder is gitignored by design. From the CLI, --workspace overrides the location.