Tasks
The Tasks tab is what the team does. Real teams have rhythms — a Monday standup, a Friday update, an inbox check at 9am. Cabinet has the same three rhythms.
The three rhythms
Tasks — one thing, runs once. "Draft the launch post." You write a brief, dispatch it, the agent works, the output lands in your folder.
Routines — a task on a schedule. "Draft the launch post every Friday at 10am." Same shape as a task, plus a cron-like schedule.
Heartbeats — a recurring check-in the agent uses to decide what to do next. "Every weekday at 9am, look at the launch room and tell me what changed." The difference between an assistant you have to summon and a teammate who shows up.
What lands back
Outputs are durable pages, not chat transcripts. A research task produces a research page. A weekly summary produces a weekly summary page. You'll be able to find it next year by ls-ing.
Every dispatched piece of work also queues a one-click human approval before anything runs that touches the outside world.
Read more
- Tasks — anatomy of a task, brief format, dispatch loop.
- Routines — schedules, triggers, history.
- Heartbeats — the rhythm that turns assistants into teammates.
- Conversations & approvals — how nothing runs without your say-so.
- Tasks vs Routines — when to pick which.