Skip to main content
The Inbox is your unified command center for managing pull requests across all your GitHub repositories. Instead of context-switching between GitHub tabs, IDE windows, and chat interfaces, the Inbox brings everything together so you can review code, trigger AI agents, and merge PRs — all from one place.

Why Use the Inbox?

Modern development teams face a paradox: AI can write code faster than ever, but the review and merge process remains a bottleneck. The Inbox solves this by making PR management as fast as code generation.
When AI agents generate PRs at scale, you need a way to review and merge them efficiently. The Inbox shows all your open PRs with real-time status — failing checks, review comments, merge conflicts — so you can take action immediately without hunting through GitHub notifications.
See a failing CI check? Click “Fix” and an AI agent will analyze the failure and create a follow-up PR with the solution. Got a nitpicky review comment? Click “Address” and let the agent handle it. The Inbox turns every PR blocker into a one-click automation.
The Inbox prefetches PR details on hover, shows diffs inline, and lets you merge without leaving the page. You maintain your flow state while staying informed about every PR’s status.

Inbox Overview

Navigate to the Inbox to see all open pull requests across your connected repositories.

PR List View

The PR list shows your open pull requests with key information at a glance:
  • Status indicators — Draft, open, or ready to merge
  • Todo badges — Count of failing checks, unresolved comments, and actionable agent sessions
  • Running agents — Spinner icon when agents are actively working on the PR
  • Repository and author — Quick context without opening the PR
  • Relative timestamps — How long ago the PR was created
Hover over any PR card to prefetch its details. When you click through, the detail view loads instantly.

Filtering PRs

Use the filters at the top of the Inbox to focus on what matters:
  • Repository — Filter by specific repositories
  • Author — Show PRs by specific team members or just your own
  • Source — Filter by GitHub PRs or agent-generated suggestions
  • Status — Focus on PRs with unresolved items (failing checks, comments, conflicts)

PR Detail View

Click any PR to open the detail view, which shows everything you need to review and merge.

Merge Status Panel

The merge status panel at the top provides a comprehensive view of merge readiness:
Merge Status Panel showing circular gauge, status summary, and merge button
Circular Gauge — Visual representation of PR health:
  • Green segments = passing checks
  • Yellow segments = pending checks
  • Red segments = failing checks
  • Purple segments = unresolved review comments
Status Summary — Quick text summary like “2 failing checks, 3 unresolved comments” Merge Button — Merge directly from the Inbox with your preferred merge method:
  • Squash and merge (default)
  • Create a merge commit
  • Rebase and merge
If required checks are failing but you have permission to override, an “Override” checkbox appears next to the merge button.

Collapsible Sections

The detail view organizes PR information into expandable sections that auto-expand when they contain actionable items:

Agent Checks Section

Shows all AI agent sessions associated with this PR:
  • Active agents — Sessions currently running with status indicators
  • Suggested workflows — Pre-configured agents that match this PR but haven’t run yet
  • Quick actions — Start, view, or manage agent sessions directly
Each agent row shows:
  • Agent/workflow name
  • Current status (running, completed, needs review, error)
  • Action buttons (View, Start, Retry)
Click “Add Agent” to create a new workflow that will automatically run on future PRs matching this repository and trigger type.

Checks Section

Lists all CI/CD checks with their status: Failing Checks
  • Expanded by default when failures exist
  • Each check shows name, duration, and app icon
  • “Fix” button triggers an agent to analyze and fix the failure
  • “Fix all” button addresses all failing checks in a single agent session
Passing Checks — Collapsed by default, expandable to verify Pending Checks — Shows spinner and “in progress” status Skipped Checks — Neutral checks that didn’t run Click any check to view detailed logs in a modal.

Review Comments Section

Displays unresolved review comments with full context:
  • Code snippet with diff hunk
  • Comment author and timestamp
  • File path and line numbers
  • “Address” button to trigger an agent that resolves the comment
  • “Resolve” button to mark as resolved
When an agent successfully addresses a review comment, the comment is automatically resolved after the agent’s PR is merged.

Merge Conflicts Section

When conflicts exist, this section provides:
  • Clear indication that conflicts block merging
  • “Resolve” button to trigger an agent that resolves conflicts automatically
  • The agent will analyze both branches and create a conflict-free merge

Tabs

The detail view includes additional tabs for deeper exploration: Files — Browse the diff with a file tree sidebar
  • Hierarchical folder structure
  • Click files to jump to their diff
  • Inline review comments shown in context
Conversation — Full PR conversation history from GitHub Tasks — All agent sessions linked to this PR with detailed status

Shipping Workflow

Here’s how to use the Inbox to maintain high velocity:

1. Triage Your PRs

Open the Inbox and scan the todo badges. Focus on PRs with:
  • Failing checks (red badge)
  • Unresolved comments (purple badge)
  • Merge conflicts (conflict indicator)

2. Fix Issues with Agents

For each blocker, use one-click agent actions:
BlockerActionWhat Happens
Failing checkClick “Fix”Agent analyzes logs, creates fix PR
Review commentClick “Address”Agent reads comment, implements change
All failing checksClick “Fix all”Agent fixes everything in one PR
Merge conflictsClick “Resolve”Agent resolves conflicts automatically

3. Review Agent Output

When agents complete, their PRs appear as new items in your Inbox. Review the generated code, approve, and merge.

4. Merge When Ready

When all checks pass and comments are resolved:
  1. Select your merge method from the dropdown
  2. Click the merge button
  3. The PR is merged without leaving the Inbox
For PRs created by agents, you can often trust the AI’s work and merge quickly. The agent has already run tests and addressed any issues.

Best Practices

Create reusable workflows for issues that recur across your codebase — linting fixes, test failures, security updates. These appear as suggested agents on matching PRs.
When multiple checks fail for related reasons (e.g., a type error causing cascading test failures), “Fix all” often produces a more coherent solution than fixing checks individually.
Check the Inbox 2-3 times per day rather than constantly. This lets agents work in the background while you focus on deep work.
Agent-generated fixes are usually correct, but always glance at the diff before merging. Look for:
  • Unexpected file changes
  • Overly complex solutions
  • Changes outside the intended scope

Keyboard Shortcuts

Navigate the Inbox efficiently with keyboard shortcuts:
ShortcutAction
j / kMove down/up in PR list
EnterOpen selected PR detail
EscapeClose detail view
mOpen merge dropdown (when in detail view)

Troubleshooting

  • Verify your GitHub App is installed with access to the repository
  • Check that you’re viewing the correct organization scope
  • Refresh the page to fetch latest PR data
  • Ensure you have sufficient credits or a valid API key configured
  • Check that the agent has access to the repository via GitHub App
  • Review the agent session logs for specific error messages
  • Check the status summary for blocking issues
  • Verify you have merge permissions on the repository
  • For protected branches, ensure required reviews are approved