Inbox

The Inbox is the second surface, and after setup it is where you spend most of your time. In the triad — Discuss to decide, Inbox to approve, Tasks to steer — the Inbox is the attention cockpit: the single place where everything that needs your judgment comes back to you. You do not watch every run or refresh every task. You let work proceed and act on what surfaces here, and that is how you stay in control without doing the work yourself.

Everything that needs you arrives in one queue

The Inbox is one workspace-scoped feed that collects attention from every domain into a single ordered list. An agent's question, an approval it needs before acting, a mention of you in a comment, a delegation request awaiting your decision, a runtime job that failed, a task assigned or updated, a task that stalled in the blocked state, a budget threshold warning — they all land in the same queue. Instead of checking the chat surface, then the task board, then the machines, you check one place, and what is there is the set of things only you can resolve.

Each item names its kind and carries a short title and body, so you can read the queue and know what each entry is asking of you before you open it. Because the queue mixes sources, it is ordered by recency rather than by domain: the most recent attention sits at the top, regardless of where it came from.

Each item links back to where it came from

Most items point back to a task and the exact timeline event that raised them. A question links to the question on its task's timeline; an approval request links to the moment the agent asked; a mention links to the comment that named you. Following the link drops you into the full history around the item, so you decide with the papertrail in front of you rather than from a stripped-down notification. Some items have no task behind them — a budget warning or a machine-level alert belongs to the workspace or a runtime, not to a single piece of work — and those link to the surface that owns them instead.

This is the through-line back to Tasks: the Inbox is a queue of pointers into the task papertrail, not a separate store of work. It tells you something needs attention and takes you to where the attention belongs.

Quick actions apply the source change

Items carry quick actions, and acting on one applies the change where it belongs. Opening the linked task, approving or rejecting a delegation, dismissing an item, jumping to the agent settings behind a runtime alert, requesting a CLI update for a machine, accepting or rejecting a proposed record, answering a workflow question, or deciding a workflow approval all change the source record that raised the item. Every item carries at least one action, so nothing in the queue is a dead-end notice: when there is no decision left to make, you can always dismiss it to clear it. The Inbox holds the attention record; the task, the runtime, the workflow, and the workspace still own their own changes. So when you approve a delegation from the Inbox, the assignment changes on the task, not only in the queue.

Which actions an item offers depends on what raised it and what your workspace role can do. The command center can surface workflow-linked questions and approvals from anywhere in the app, but it still submits the same answer, approval, or rejection that the Inbox action would submit. Handling an item moves it out of your active queue: you read it, complete it, or archive it, and the count drops.

Proposals also wait on each resource's page

The Inbox pushes a proposal to you the moment an agent makes one, but it is not the only place to clear it. Every record an agent can propose — agents, teams, skills, projects, goals, workflows, and tasks — carries a Proposed tab beside its Active and Archived views, listing the records awaiting your decision with the proposing agent and the rationale it gave. Opening a row previews the actual proposed record — a workflow's steps, an agent's model and instructions, a task's project, priority, and due date — so you review the real thing before deciding, not just its title. Approve activates the record into the Active view; reject clears it with a reason saved back for the agent. The Inbox is the push surface that brings one proposal to you the moment it lands; the Proposed tab is the pull surface where you sit on a resource's own page and work down the backlog of everything pending there. Both submit the same decision, and your role decides whether you see the approve and reject controls at all.

A morning email brings you back

You do not have to be in the app to know where things stand. Once a day, at 8:00 in your timezone, Task Machine sends a morning digest — one email per workspace that mirrors the workspace home: what is waiting on your approval, what is blocked, what finished yesterday, what is in progress, and where each budget stands in its own currency. Every line links straight back into the workspace, so the email is a way in, not a dead end. Quiet days stay quiet: when nothing happened and nothing needs you, no email is sent, and the digest only ever contains what you are allowed to see, composed for you.

You control the digest from notification settings, where it sits as a row in the notification table — turn the daily email off entirely there. The timezone that decides when "morning" is lives in account settings. New accounts have the digest on, with the timezone guessed from where you signed up; change either at any time.

The Inbox updates live

The Inbox reflects the workspace as it changes, without a reload. When an agent on a connected machine asks a question, finishes a task, or hits a failure, the item appears. When you or anyone else reads, completes, or archives an item in another session, already-open Inbox and dashboard views update to match. The count you see is the count that is actually waiting, which is what lets the Inbox be the surface you trust to tell you when something needs you.

From here, the items themselves trace back to the third surface. Most of what arrives was raised on a task, so see Tasks for the record they point into and Comments and mentions for how discussion on a task turns into attention here.