A scripted example, not a real replay. From one instruction to the completion report, every step is visible.
DEMO
Session flow
InstructionStep 1/8
Ask for yesterday's order count
Open the admin console and pull yesterday's order volume.
A one-line morning request goes to the agent. It breaks the task down by itself: which console, which computer, which table — no human decomposition needed.
The task is created and locked onto the finance computer comp-finance-01.
BrowserStep 2/8
Open the order console
Open a browser session on the finance computer and enter the order console.
The agent opens an isolated browser session on comp-finance-01 and signs into the order console under your authorization; the session closes when done, leaving no standing side door.
The order console is ready, the page is loaded, and the query can start.
computerId: comp-finance-01
RoutingStep 3/8
computerId routing
Every tool call carries its computerId.
Browser, terminal, and file operations are all pinned to comp-finance-01. A wrong target or an offline machine fails explicitly — nothing quietly switches computers.
The routing surface is locked: this session touches only the finance machine.
computerId: comp-finance-01
TerminalStep 4/8
Run the stats script
Run the statistics script in the terminal to compile yesterday's orders.
The script aggregates order count, refunds, and revenue hour by hour into a temporary result file; every command and its output stay on the audit record.
Yesterday's numbers are compiled and waiting for the report.
computerId: comp-finance-01
FileStep 5/8
Fill the daily report
Edit the report file and write the statistics into the daily report.
The agent opens the daily template and fills in the summary numbers; history stays untouched, and only today's section is appended.
The report is updated and moves to approval before submission.
computerId: comp-finance-01
ApprovalStep 6/8
Human approval
Wait for human approval before submitting the report.
The agent stops on purpose and sends the change summary into the approval queue; you read the numbers, leave a note, and approve or reject.
Approved — the workflow continues.
computerId: comp-finance-01
BrowserStep 7/8
Read back and verify
Return to the console and check the numbers match.
Submission is not the end. The agent reloads the console page and compares every report figure against the live numbers to rule out writing errors.
Everything matches, and the daily report takes effect.
computerId: comp-finance-01
DoneStep 8/8
Report completion
Report the result: yesterday's orders are counted and archived.
The agent hands over an execution summary: what ran, what changed, what was approved — each step timestamped and traceable in the audit record.
You only read the summary. Tomorrow morning, it does it again.