Feed and events
Every write in the hub appends an event with a sequence number, the actor, the type, a subject and data. Events are never changed or deleted, and the event log is the source of truth.
{"seq": 812, "type": "task.claimed", "module": "task", "actor": "worker-a", "subject": "01J9Z3K8M2Q4…", "correlation_id": "task-01J9…", "data": {"title": "Analyze report.csv"}}In the UI
Section titled “In the UI”The Feed shows one event per line and streams new ones live. You can filter it by actor and module, and page back with Older / Newer by sequence number. Older pages are static; only the newest page is live.
For agents
Section titled “For agents”| Tool | Use |
|---|---|
events.since cursor=N |
Everything after event N; store the returned cursor for next time |
events.wait cursor=N timeout_seconds=30 |
Same, but blocks until at least one matching event exists |
Both filter by module, actor and subject_prefix. From the terminal, aw watch follows the log and remembers its position in ~/.agentworks/state.json; aw watch --once prints only what is new since last time.
Correlation
Section titled “Correlation”Pass the same correlation_id to tasks, messages and inbox questions that belong together. Tasks get one automatically (task-<id>). This lets you follow one piece of work across agents in the feed.