Inbox
One queue for every human decision your agents will hit.
The inbox is where an agent goes when it needs you. It's a real surface, not a notification bucket: it has its own page, deep links, bulk actions, scoped widgets, and a routing model based on who has access to the underlying resource.
Three decision kinds
| Kind | What it asks | Common source |
|---|---|---|
plan_review | Is this plan OK to execute? | A workflow node that requires plan review |
approval_gate | Can I do this specific action? (e.g. a risky path edit) | A workflow node configured with risky paths |
context_candidate | I learned something. Should we add it to the vault? | The context engine when an agent proposes new memory |
A reviewer sees a single queue across all three kinds. Filters narrow.
Status
| Status | Meaning |
|---|---|
open | Needs a decision. |
resolved | Decision recorded. The daemon can read the result and continue. |
dismissed | Closed without a decision (rare, e.g. expired or superseded). |
Routing
An inbox item routes by resource access, not by project. There is no project intermediary. Resources flow direct to teams.
The flow:
- The workflow node specifies the audience (a share group, a role, or a specific user).
- The platform expands that audience against current resource ACLs.
- Every member of the expanded set sees the item.
- The first to resolve it wins. The rest see the resolved state with the decider's name.
You can preview routing without resolving anything:
POST /api/resources/{workspace}/inbox-items/policy-simulationScoped embeds
The same inbox renders, scoped, inside other surfaces:
- Workflow run detail shows decisions for this run only.
- Vault detail shows pending context candidates for this vault only.
- Plan detail shows feedback and review state for this plan only.
Same data, scoped filter. Lets you stay in flow without context-switching to a global list.
Notifications
When an item lands you can be notified through:
- In-app (the inbox itself)
- Webhook delivery to an endpoint you configure (Slack, Linear, your own consumer)
Native push is not wired yet
A native iOS / Android push channel is not wired today. The phone-notification path works through web push or Slack for now.
What "decide from anywhere" means today
An inbox item carries enough context that you can decide from web (desktop or mobile-responsive) without opening the laptop the agent is running on. The agent reads the resolved decision via its workflow-run subscription and continues, or stops, depending on the answer.
Related
- Plans
- Team Context for where context candidates come from
- Workflows for where routing is declared
- API for the REST surface