Skip to main content
The Inbox is built for working down a list fast: open an item, act on it, move to the next — without losing your place or leaving the page. This page covers the mechanics.

The detail pane

Clicking a row (or pressing Enter on the highlighted one) opens a detail pane that pushes in from the right — the list compresses beside it and stays fully interactive, reading-pane style. There’s no modal and no overlay.
  • Resize it by dragging the handle on the pane’s left edge. Your width sticks between visits; by default it takes about half the space, and the list always keeps enough room to stay readable.
  • It stays open after you act. Approving, rejecting, or clearing an item doesn’t slam the pane shut — it switches to a read-only “what happened” face, so you can confirm the outcome before moving on.
  • Close it with the X in its header or Esc.
The pane leads with the agent’s own voice — the agent’s name and its one-line summary of what it did or needs — followed by the full item: the drafted artifact, the account, the due clock, and the actions.

Deciding approvals in place

An approval row is decided right in the pane — no separate approval screen:
  • Most drafts render an editable face: review the draft, optionally edit it, then Approve (or approve with your edits). Your edits are what gets sent.
  • Reject reveals a reason box — the reason goes back to the agent, so say what’s wrong (“The pricing is wrong — use the renewed rate”). A reason is required.
  • A decision commits immediately and can’t be undone; the paused agent resumes with your answer.
A few approval types keep their decision on a dedicated page (for example, some workflow approvals with richer forms). Those rows show an open-the-page button instead of inline Approve/Reject — the Inbox never offers a decision it can’t actually commit.

”Already sent” vs “Needs your OK”

Autonomy in Thread is per action, and the chip on each agent item tells you which side of the line it landed on:
  • Needs your OK — the agent paused before acting. The item is a pending decision; nothing has gone out.
  • Already sent — the agent acted autonomously and this row is the record. There’s nothing to approve; review it and clear it.

Clearing items

Record-style items (notifications, wins, alerts) offer two clear verbs, and the difference matters for your team’s stats:
  • Done — counts as handled.
  • Dismiss without acting — clears it without counting as handled.
Purely informational items collapse the pair into a single Clear. Clears have a brief undo window — an Undo toast brings the row straight back.
Some exception kinds can’t be dismissed while the underlying problem is live — a blocked agent, a failed run, a triggered kill switch, a stuck account, a stalled milestone. Dismissing one would just hide a live problem, so those rows clear automatically when the condition is actually addressed (the agent resumes, the retry succeeds, the switch is lifted). You can still snooze or reassign them in the meantime.
Snooze is always available: 1 hour, 4 hours, tomorrow, or next week. Snoozed items sit in the Snoozed shelf and return to the list on schedule.

Items resolve themselves when addressed elsewhere

You never need to come back and tidy up. If an item is handled somewhere other than the Inbox — the customer replies, the agent resumes, the approval is decided from an email link, a teammate handles it — the row resolves on its own and moves to history. One fact, one row: duplicate signals about the same thing collapse into the item you already have.

Reassigning and escalating

From a row’s ··· menu (or the detail pane’s More menu) you can hand an item off without opening anything else:
  • Reassign — pick a teammate; the item moves to their Inbox. Works on a single row or on a multi-row selection via the checkboxes and batch bar.
  • Escalate — a deliberate single-item hand-off that carries an escalation marker, so the recipient knows it’s not a routine reassign.
  • Send to external approver — route an approval to someone outside Thread. See External approvals.

Due chips

Action-needed items carry a live due chip — “4h left”, “due now”, “overdue 2h” — that counts down on the row and in the pane. Overdue items float to the top of Needs you, and the Overdue stat in the header tracks the total. Informational items carry no deadline.

Saved views

Any combination of filters and sort can be saved as a named view in the left rail, alongside the four built-ins (All open, My approvals, Overdue, Due today):
1

Shape the view

Apply the filters you want — categories, accounts, status, assignee, urgency, a sort order.
2

Save it

Click Save current view in the rail’s Saved views section and name it.
3

Manage it

Your custom views can be renamed or deleted from the rail at any time. Clicking one applies its whole snapshot — filters, sort, everything.
Saved views are personal — yours don’t appear in teammates’ rails.

Keyboard shortcuts