Feature · Activity
Activity
See what your AI employees, people and agents did in each work system.
How it works
What it shows
Activity lists each action with its time, who did it, the system, one sentence about what happened, and whether it was a read or a write. A failed or denied action is marked. A row links to the task and to the changed item when a link exists.
It works with or without AI employees. A person, an AI employee and an outside agent all appear in the same list.
Where the entries come from
- Work that your AI employees do.
- The work systems you connect, such as your code host, task board and chat.
- Outside agents and tools that report their own work.
Activity shows only what these sources record.
Find something
Select a time range, a person or agent, a provider, or one or more systems. The address of the page keeps your selection, so you can share the view.
Systems touched counts reads and writes for each system in the view. A task page shows the same summary for that task.
When a source could not be read
If Activity could not read a source in full, the page says which one. An empty list with such a notice means not known. It does not mean that nothing happened.
Report from your own agent or tool
Select Report from an agent to see an example request. Your agent sends each action with a short summary, the system and the result. It needs an API token with full access. The entry shows the agent and the person whose token it used.
From the help article Activity, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
ViewerlistActivityWhat any actor (AI employee, member, external agent or login, the platform) did across systems, newest first. Filter by actor, system, provider, work item and time.
Types:
ListActivityRequestreturnsListActivityResult
AdminNo API tokenssaveActivityPeopleFor owners and admins: say who is the same person in Activity.
Types:
SaveActivityPeopleRequestreturnsSaveActivityPeopleResult
MemberNo API tokenscreateRunnerPairCreates a runner pair.
Types:
import('./runner.js').CreateRunnerPairRequestreturnsimport('./runner.js').CreateRunnerPairResult
AdmindeleteFormatTemplateDelete an organization template that no delivery uses.
Types:
DeleteFormatTemplateRequestreturns{ deleted: true }
AdminpostFormatNowPost a delivery for a day (default today) to its channel now. Returns what was posted and where.
Types:
PostFormatNowRequestreturnsPostFormatNowResult
AdminsaveFormatDeliveryCreate or change a delivery: a template posted to a Slack channel at a time on chosen weekdays. A Slack channel id or name is checked against the organization Slack connection and resolved before it is saved.
Types:
SaveFormatDeliveryRequestreturnsSaveFormatDeliveryResult
AdmindeleteFormatDeliveryDelete a delivery. Its past posts stay in the audit log.
Types:
DeleteFormatDeliveryRequestreturns{ deleted: true }
ViewerpreviewFormatApply a template (saved, or given inline) to the timeline for a day or a range, optionally for one actor or one work item. Returns the document, plain text, Markdown and the Slack message.
Types:
PreviewFormatRequestreturnsPreviewFormatResult
AdminsaveFormatTemplateSave an organization template: a header, sections with filters and line patterns that use slots from the slot catalog. An error names the field and the slot.
Types:
SaveFormatTemplateRequestreturnsSaveFormatTemplateResult
Screens
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Policy changed
- Activity people changed
- Local runner created
- Local runner delegates changed
- Local runner device approved
- Local runner device denied
- Local runner device token issued
- Local runner registered
- Local runner revoked
- Release recorded
- Worker sandbox observed