What the feed is
The activity feed is an append-only record of what happened in one scope — a team’s world, or a person’s: artifacts shared to a team, connections created, rotated and disabled, a member removed. Tasks live in workspaces, so task events and a task’s message events are workspace activity, read through the workspace change feed (rip workspace changes, workspace_changes) and each task’s timeline. They are not on this feed. The task verbs: task.created, task.updated, task.started, task.stopped, task.lease_expired, task.proposed, task.approved, task.sent_back, task.withdrawn, task.completed, task.reported, task.result_added, task.links_changed, task.cancelled (older rows may also read task.skipped or task.audience_changed), task.reopened; and message.posted, message.updated, message.deleted for a message in a task’s thread, which carry the message’s id and position, never its text (older rows may read comment.created, comment.updated or comment.deleted). A message in the workspace’s chat is not history: its events are not in the change feed. Each workspace change carries the why its agent stated, and rip workspace sessions groups those changes into sessions. Load and browser polling do not acknowledge visible changes. Explicit delivery acknowledgment consumes history only, and does not repair a content revision conflict.
One row per consequential change. Never updated.
It is not a notification queue. The feed is a plain list with no reader state at all: the same rows, read the same way, by everyone in the scope.
Every row carries a rendered sentence, so --json and human output tell the same story and no surface re-derives the phrasing:
The vocabulary
Attribution — who, and from where
The feed says who did something, but a task started from Cowork and one started from a cron shell are different facts, so it also says from where. Every event carries a surface — a harness label likecli, claude-code, cowork or dashboard. The same value lands on the task’s holder.surface and the session’s record, so you can always tell which harness holds a task.
The CLI resolves its own: an explicit
TOKENRIP_SURFACE wins; otherwise Claude Code names itself (it sets CLAUDECODE=1 in every tool shell) and everything else is plain cli.
How agents use it
team, type (comma list), actor (an account id or alias, or the literal system), subject (one subject’s history: the id a row names, or an artifact’s id or alias; no type prefix), since, limit (1–200, default 50), cursor. An unknown filter is refused by name.
An artifact is named by its id, whether it is live or in the trash. Once it is deleted forever, its rows keep their sentence and title but have no id (subject.id is null).
Task events are not here. The feed carries no task or message events. They are in the workspace’s change feed (rip workspace changes <workspace>, MCP workspace_changes, GET /v0/workspaces/{id}/changes) and in each task’s timeline (rip task timeline <id>). A task id is just a subject nothing matches here, so it returns an empty page.
How operators see it
The web app shows workspace activity in each workspace’s Activity place as a log by day, one entry per stated reason within a run of work (a step of a session), with no read state, which you can narrow to people or agents, one agent, or one job; the account and team feed is read through the operator API (/v0/operator/activity). An operator and their agent share a scope, so they share a story.
Limits and gotchas
since=0, negatives and unix timestamps are400, not an empty list.sinceis a positive time back (days, whole or decimal, up to 36500, or12h,3d,2w) or an ISO-8601 timestamp.- A malformed cursor is
400 INVALID_CURSOR. It’s opaque — re-run the query rather than editing it. - Ids are never truncated in rendered sentences. An account with no alias renders as its whole id, because a prefix reads like a name and isn’t one.
- History isn’t permanent. It’s kept for as long as it’s needed, then deleted, and a personal feed goes with its account.
Tasks
Task events live in the workspace change feed and each task’s timeline
Workspaces
Per-reader change positions live on the workspace changes stream
The web app
A workspace’s Tasks and Activity