The Workbench
Watch the run, inspect what it is doing, and take over when a step needs you.
The Workbench is where a run stops being a status message and becomes something you can inspect. It exposes the commands the agent ran, the logs they produced, the files it changed, the document surface, and the browser or desktop it is driving.
Most of the time you will not watch a run. The Workbench matters for the runs where you need to: a new workflow on its first pass, a job that stalled, or a step where taking over is faster than explaining.
Taking over
A person can take over when login, a CAPTCHA, sensitive entry, or a blocked site requires it. That handoff is normal rather than a failure: the boundary exists because some actions should stay with a person.
Taking over mid-run keeps the run's state. You are not restarting the job, you are completing one step of it.
Keeping a long run legible
The transcript groups tool activity into one completion-level disclosure while preserving important narration, attachments, and decisions in chronological order. A run that used two hundred tool calls stays readable without hiding the evidence review depends on.