Inbox
The bell in the top bar of every page is your inbox. Agents and fleet itself post to it when they need you. The number on the bell is the open items.
| Kind | What it is | What you do |
|---|---|---|
| Brief | A summary from an agent | Reply, or dismiss |
| Question | An agent asks you something (the ask tool) |
Answer it in the box |
| Approval | An agent wants a yes before it acts | Approve (you may edit the text first), or reject with a reason |
| Proposal | An agent proposes a change to config, with evidence | Approve, change the target layer first, or reject with a reason |
| Alert | Something broke: an incident, the trunk guard, a token | Snooze for an hour, or dismiss |
| Info | News that needs no action | Dismiss |
- Your answer goes back to the agent. An answer, an approval or a rejection reaches the agent that posted the item as a message from you, and starts its next turn.
- An agent that asks for an approval sleeps. It shows waiting for you, and no process runs for it until you approve, reject or dismiss the item, or send it a message. Your answer starts its next turn, at the top of the same conversation. Dismissing it tells the agent "no".
- A rejected proposal is muted. The same proposal from the same agent is refused after you reject it, and the agent gets your reason.
- A proposal to the fleet layer needs an admin to approve it.
- Done in the bell shows the items you closed, with what you answered.
- Answering elsewhere counts. A question answered by a Telegram reply or a chat message closes in the inbox too.
Delivery
Every item shows in the bell. Delivery in the bell picks the kinds that also go to your
linked Telegram chat (fleet notify link telegram). The default is questions, approvals and
alerts. Quiet hours hold Telegram until they end, in your time zone; the bell still shows the
item at once. The same hour twice means no quiet hours.
For agents and scripts
An agent posts with the inbox_post MCP tool: a kind, a one-line title, and a body with the
detail. An agent that must wait for a time rather than for you calls the wait MCP tool (minutes,
or a time up to 7 days ahead, and what it waits for). It shows waiting, no process runs, and
its next turn starts at that time, or sooner when a message reaches it. A person or a script posts with POST /v1/inbox and a person's token. See the API
reference for GET /v1/inbox, POST /v1/inbox/{id}/act and /v1/inbox/settings.