Skip to content

Inbox

The Inbox is where your agents reach you. When an agent needs an answer, hits a blocker, finishes something worth showing, or wants to recommend a connection, it sends a message here instead of failing silently, at the priority it judges right — questions default to Urgent.

This is the other half of delegation. Handing work to agents only saves time if you don’t have to babysit the runs, and you can stop babysitting only if the moments that genuinely need you reliably surface. The Inbox is that contract: an agent that needs a decision, a credential, or a review sends the item here with a priority instead of stalling quietly — including assignment runs that hit a blocker on a morning nobody was watching.

Example items, one per priority:

  • Urgent — a question the agent needs answered: “The export has two revenue columns, booked and recognized — which should the pipeline report use?” The agent is waiting on you, so questions arrive Urgent unless the agent judges otherwise.
  • Important — a blocker on scheduled work that isn’t racing a clock: “The CRM credentials have expired; Monday’s pipeline report can’t run until the integration is reconnected.” Worth your attention today, not this minute.
  • Normal — routine updates and ambient context: “Weekly competitor sweep finished — two rows updated, no pricing changes.” Skim it now or let it wait.

An issue that is waiting on you can land here too, with an Open issue link to its record.

Tabs slice the list by priority — All, Urgent (“needs your attention soon”), Important (“worth your attention but not time-sensitive”), and Normal (“routine updates and ambient context”) — with a Done view for items you’ve cleared and a search box across the lot. Mark items done or unread, Move them to another priority, or Snooze them (later today, tomorrow, later this week, this weekend, next week, or a date and time you pick).

The agent’s priority is a starting point, and you can override it: if a Normal update turns out to matter, move it up; if an Important item can wait for Friday’s review, snooze it to later this week. Snoozing to the time you’ll actually act keeps the queue honest — “this weekend” for reading, “next week” for a decision that’s waiting on something else.

The list is built for the keyboard: J and K step through items, R replies, F forwards, E marks done, H snoozes for an hour, X selects items for bulk actions, and ? lists the rest.

Open an item and it’s a thread: Reply to answer the agent in place, Forward it to another agent, or open the full session for the context. Integration recommendations come with one-click Connect (or Don’t ask again). Attached work products open right from the thread.

Reply covers the common case — the revenue-column question above needs one sentence (“use recognized”), typed right in the thread, and the waiting session picks up from your answer. Forward covers the question that reached the wrong desk: an agent asks you about data another agent owns, and forwarding puts the question where the answer is. And when a one-line item isn’t enough context to decide, the session shows exactly what the agent was doing when it wrote to you. A recommendation works the same way in miniature: an agent that keeps needing data from a system you haven’t connected can suggest the integration, and Connect acts on it from the thread — or Don’t ask again closes the subject.

The Inbox can follow you. In Settings → Account → Notifications, choose for each channel — Slack, Email, and Text message — how much reaches you there: urgent only, important and urgent, everything, or off. Out of the box, Slack carries important and urgent items once you’ve linked your Slack account, texts carry only urgent ones once you’ve verified a mobile number, and email is off.

Set your working hours and choose what each channel does outside them: hold until you are back, let only urgent items through, or send anyway. A Pause quiets everything for an hour, four hours, until morning, or a week. You can also set different rules for a particular workspace or agent, so a noisy research agent stays in the app while the one running payroll can text you.

Every item is in the Inbox whichever channels it also reached, and a reply on any of them — a Slack reply, an email reply, a text — lands in the same thread and resumes the waiting session exactly as replying in the app does.

For the complete site index, see llms.txt.