Notifications and inbox
The inbox is where an agent reaches you when you are not looking at its conversation: a run finished, a routine failed, something is waiting on your approval.
When to use it
Section titled “When to use it”The inbox exists because agents keep working after you close the tab. It is the answer to “what happened while I was away, and what needs me now”.
What lands there
Section titled “What lands there”| Notification | Sent when |
|---|---|
| Agent replied | A conversation run finished |
| Routine completed | A routine run finished |
| Routine failed | A routine failed repeatedly and was paused |
| Waiting for you | A run is paused on an approval or a question |
Ordinary progress inside a run does not notify you — tool calls appear in the conversation, not in the inbox.
Reading it
Section titled “Reading it”The inbox has two lists: Inbox for anything you have not dealt with, and Done for what you have cleared. Items waiting on you are promoted to their own section at the top, so a request for approval does not sit buried under twenty finished runs. Filters narrow the list to replies, errors, or system messages.
Selecting an item takes you to the conversation, routine, or artifact it refers to. That is where you act on it — including approvals, which are always answered in the conversation itself.
Keeping it useful
Section titled “Keeping it useful”An inbox that is always full stops being read. Two habits keep it signal:
- Clear finished runs as you go. Anything you have looked at belongs in Done.
- Let routines summarize, not narrate. A daily routine that produces one artifact is one notification; one that sends interim updates is several.
Limits
Section titled “Limits”- Notifications tell you something happened; they are not where you act. Approvals and questions are answered in the conversation.
- An item cannot be marked unread again once it is cleared.
- Notifications are per account, covering all your agents. There is no per-agent inbox.