Skip to main content
The Inbox is your decision center. It is not a copy of your chats or your issue board. It surfaces only the things that need an action from you right now: a plan to approve, finished work to review, a blocked issue, a failed code review, or a proposal from an agent. When the Inbox is empty, the team is moving on its own. When something lands there, your team is waiting on a decision only you can make.
The Inbox shows items for your active workspace. Switch workspaces from the sidebar and the Inbox refreshes to that workspace’s pending decisions.

​
What lands in your Inbox

The Inbox is deliberately narrow. Everyday chats and ordinary open issues stay on their own screens. Only these five kinds of items appear, each with the action built right into the row.

Proposals

Agents propose work: a hiring plan, a source specialist, or analysis of a Sentry error or an observability signal. You approve, open, or dismiss.

Plans awaiting approval

An epic was broken into sub-issues and is waiting for your go-ahead before the team executes.

Work in review

Finished sub-issues sitting in review, grouped by their parent task. You approve or send back for changes.

Needs attention

Blocked issues and code reviews that failed. These do not have approve or reject, but you can open or dismiss them.
The Inbox refreshes on its own every few seconds, so new plans, reviews and blockers appear without you reloading. A small count badge on each section tells you how many items are waiting.

​
How it works

The Inbox reads your issues, agents and recent activity for the active workspace, then filters down to only what is actionable. Some highlights of the logic so you know what to expect:
A plan appears only when the epic still needs your approval and has real, non-cancelled sub-issues under it. An epic that is already done or cancelled never asks for approval, so you do not chase phantom pending items.
When the system routes work to a reviewer agent through the reporting chain, that automatic review resolves on its own and does not clutter your Inbox. Only work that needs a required human approver shows up in the In review section.
Sub-issues in review are grouped under their parent epic so you can scan and approve them together. Orphan sub-issues (no parent) fall into an Other reviews group.
Proposals are de-duplicated per session, keeping the most recent. A hiring proposal disappears once your team already exists (any non-orchestrator agent), and a source specialist proposal disappears once that source no longer needs a new agent.

​
Acting on each item

Every row carries its action inline, so you rarely need to leave the Inbox. Click the body of any row to open the related issue, session or screen for full context first.
Proposals come from your agents and vary by type. Each row has a primary action, a secondary link for context, and a dismiss (X).
  • Sentry issue: Click Analyze and fix to start a session that investigates and fixes the error, or use Open in Sentry to view it in your browser. The body opens your Sentry screen.
  • Observability signal (New Relic or Better Stack): Click Analyze and fix to open a session on the signal, or Open to view the source. Incidents are flagged distinctly from errors and logs.
  • Source specialist: Click Approve and create to create a specialist agent for that source, or View knowledge to inspect the source first. The reason for the proposal is shown in the row.
  • Other proposals (such as a hiring plan): Click the row to open the originating session and decide there.

​
Approving a plan, step by step

1

Open the Inbox

Click Inbox in the sidebar. Find the Plans section near the top.
2

Read the plan

Click View plan to open the epic and review the sub-issues your team intends to execute. Make sure the breakdown matches your intent.
3

Approve and execute

Back in the Inbox, click Approve and execute. The row shows a spinner while it works, then the team begins. A toast confirms the result.
4

Watch it move to review

As sub-issues finish, they reappear in the In review section of the Inbox, ready for your approval.

​
Reviewing finished work, step by step

1

Find the review group

In the In review section, locate the group for the parent task you care about.
2

Inspect a sub-issue

Click any sub-issue to open it and confirm the change is what you wanted.
3

Approve or send back

Use the green check to approve, or the red X to send it back for changes. Approve the whole group at once with Approve all when you are confident.

​
Dismissing versus deciding

Some items are decisions that change the underlying issue. Others are just noise you want out of your view. The Inbox treats these differently.
Approve and Send back for changes change the issue’s real status (done or in progress). Dismiss and Clear only hide the item locally on this machine. They do not change the issue.
Dismissing a blocked issue or a failed review hides it from the Needs attention section without touching the issue. The dismissal is stored locally, so the item stays hidden until something about it changes.
A dismissed issue reappears if it is updated (its update timestamp changes), so a blocker you cleared will resurface if the situation actually changes. Dismissed activity events stay hidden by their event id.
The Clear button in the Needs attention header dismisses all visible blocked issues and failed reviews at once. You get a confirmation toast. This is a clean-up action, not a resolution.

​
When the Inbox is empty

If there is nothing waiting, you see an all-clear state with a green check. That means no plans need approval, nothing is in review, nothing is blocked, and there are no open proposals. Your team is working without needing you.
Treat an empty Inbox as the goal of each working session. If items pile up, your team is blocked on your decisions. Clear plans and reviews first, since they unblock execution, then triage the Needs attention section.

​
What to do next

Issues and epics

See the full board behind your plans and reviews, and dig into any issue the Inbox links to.

Agents

Manage the specialists your proposals create and see who is assigned to what.

Chat

Talk to an agent directly when a decision needs a conversation, not just an approval.

Knowledge

Review the sources behind source specialist proposals before approving them.