Tasks shows the work your agents have been given, one row per task, with what it touched and how long it ran.
A row can be there before its summary and Work Type are — expect those within about two hours of a task finishing, and until they land the row shows its first prompt in place of a summary. The Logs page has the individual calls immediately.
What’s on the page
Charts
Selecting a slice or bar filters the table to it; selecting it again clears the filter.
Table
Headed Tasks with the total count.
Twenty tasks to a page.
Repository attribution
Repository and organization figures cover five tools: Cursor, Claude Code, Augment Code, Codex and Copilot. Turns with no repository are grouped as Unattributed in Activity by Git Org, and a task with no repository shows a dash in Git Repo. A turn that touched two organizations counts in each, so the slices can add up to more than the turn total.Filters and controls
Time range
24 Hours · 3 days · 7 days · 1 month, with a custom range of up to 31 days.Filters
Policy Enforcement
Policy Enforcement, beside the column picker, keeps only the tasks a policy acted on. The same panel appears on Users, on a developer’s task list and inside a task’s trace, each counting its own thing — tasks here, enforcements on Users, turns in a trace. The panel has two views, with Clear to drop every pick:
Reading the grid:
- A blank cell is a pairing that cannot happen — Data policies never warn or ask over Slack, and Skills policies only inject.
- A dash cell is possible but not set up: no active policy produces that outcome. Hover it for the reason, such as No Slack Approval policy set up or No Skills policy set up.
- A row or column heading selects every available cell in it (Select every Block cell, Select every Terminal cell).
- Picks widen within a view and narrow across them: a task is kept when it matches any picked cell, and — if you also picked policies — any picked policy too. Picking only policies keeps tasks any of them acted on.