Skip to Content
Desktop AppInbox

Inbox

The Inbox view is a focused triage queue for threads that need human attention. Where Overview is a broad dashboard, the Inbox is the “what should I look at next” list.

The component is apps/desktop/src/renderer/components/InboxView.tsx.

What shows up here

By default, the Inbox surfaces threads in these states:

  • approval / Needs approval — pipeline paused after review because the effective approval setting for that run requires a human sign-off before execution
  • failed — any phase errored out
  • completed — PR opened and ready for you to review/read
  • Verification-exhausted — verifier ran out of retries without passing
  • ci_blocked — linked PR checks are failing

Items remain in the Inbox badge queue until you explicitly dismiss them.

Row layout

Each row shows:

  • Current phase / state
  • Issue title
  • Time since last state change
  • Primary action button (View, Dismiss)

“Go to issue”

Clicking a row navigates you into the thread’s project and opens the IssueDetail overlay. This is the main reason the Inbox exists as a separate surface: it’s optimized for “see the problem, open it, fix it, move on” without sidebar juggling.

Filtering

Use the controls at the top to:

  • Sort newest vs oldest
  • Toggle Needs approval to isolate only true human-approval gates

When the Needs approval filter is enabled, Inbox hides failures, completed runs, and CI-blocked rows so you can focus only on work that is still waiting on a human decision. Once you approve a run, it leaves this filter even if execution has to wait for capacity.

Last updated on
InsightsCosts