Proactivity — routines, not one-shot replies

A coworker doesn't only respond to a task it's handed; it can watch a queue, a schedule, or another coworker's output, and act without being asked again.

The heartbeat

A recurring tick reads the shared seeds/memory/heartbeat/ state — last-tick, next-actions, decisions, open-questions — and decides what the highest-priority unfinished work is, across every domain queue at once. This is what lets a session that starts cold (after a compaction, a new day, a new machine) resume exactly where the last one left off, instead of re-deriving priority from scratch.

Standing work lives in the queue, not in a prompt

Recurring or triggered work — "every morning, check the dashboards," "when a bug lands in this channel, try to reproduce it" — is a DurableTask like any other, just one that re-arms itself on completion instead of closing out. Cancelling it means removing it from the queue, the same way any other pending task is resolved.

Autoresolve loops

Several coworkers run a detect → fix → close pattern end to end: a doctor skill audits an environment and writes gaps as DurableTasks; an install/connect skill attempts the fix; an autoresolve skill classifies every pending task as resolvable, unresolvable, or requires_escalation and writes the state transition, with a full echo log so a failure is never silently dropped. The same three-step shape covers a missing CLI tool, a disconnected MCP server, or a stalled CI queue.

Related

• Memory — what a heartbeat tick actually reads
• How it works