Runs and activity

Every piece of work becomes a run you can read like a story: what happened, how, what it produced, and what it cost.

Verse never does work invisibly. Whether you asked in chat, a schedule fired, or an employee acted on its own, the result is a run on the Runs page.

The list

If anything is waiting on you, a Needs action table sits at the top; see Approvals. Below it, All activity lists every run with who did it, a short plain language description of what it did, when, the apps it touched, and its status: Running, Completed, Failed, Cancelled, Skipped, or Queued. Running work has a cancel button right in the row.

Note

Descriptions are written by the AI after the work finishes, as a plain summary of what actually happened, so the list reads like a work log rather than a server log.

Opening a run

Expand any employee run and you get the full review:

The outcome. Status, the headline, and a one line summary of what was accomplished. If the employee used its browser or computer, there's a Watch what it did link to the session replay.
Activity details. Trigger, start and finish times, duration, and credits used.
How it got done. The timeline: each milestone in the employee's own words, with per step timing.
What it produced. Deliverable cards for anything openable: documents, spreadsheets, slides, Notion pages, images, mini apps.
Feedback. Four reactions, from Great to Off. Reactions steer future work.
Technical details. Collapsed by default: the raw trace, for when you want to see every tool call.

Workflow runs expand into a per step trace instead: each node, its input and output, timing, and where it failed if it did.

Elsewhere in the app

The dashboard's Live activity stream is the same data, newest first, updating in real time. Each employee's Workspace tab has an Activity Feed scoped to just them. And a workflow's editor has a Run history tab scoped to just that workflow.