Review inbox: all your agents’ finished work in one list

With several agents running at once, opening each one to see whether it’s done, what it changed and what deserves a closer look takes time. The review inbox collects finished work from every agent across all your projects into one list, and each card shows what you need to make the call.

One list in the right panel

The review inbox is a tab in the right panel, with a badge counting the work waiting for you. It covers every agent in every project: an agent in a worktree has its branch compared with the default branch, and an agent in the project folder has its uncommitted changes checked. The list refreshes after every finished turn.

What each card shows

A card tells you where to look before you open anything.

  • Changed files, each with its added and removed line counts.
  • Risk notes: migrations, auth or security code, dependency files, CI and infrastructure files, secret files such as .env.
  • Size notes: a large change of 800 lines or more, a big deletion of 300 lines or more, no tests added.
  • The Verify result and the agent’s last reply.
  • Tap a file to open its diff, unified or split.

Three decisions

Every piece of work has three ways forward, right on the card.

  • Approve: the work leaves the list. If the agent changes it later, the card comes back.
  • Send to the merge queue: the branch is queued to land on the main branch in turn.
  • Send back: write a note and the work returns to the agent with it.

How to use it

  1. 1

    Give your agents their work, in a worktree or in the project folder.

  2. 2

    When an agent finishes a turn, check the badge on the review inbox tab in the right panel.

  3. 3

    Read the card’s risk notes and Verify result, and tap files to see their diffs if needed.

  4. 4

    Approve, send to the merge queue, or send it back to the agent with a note.

Questions

What work does the review inbox show?

Finished work from every agent in every project. For worktree agents it shows the branch’s difference from the default branch; for agents in the project folder it shows uncommitted changes.

Does approved work come back?

Only if it changes. If the agent keeps working on it and makes new changes, the card returns.

What do the risk notes look for?

Migrations, auth and security code, dependency, CI and infrastructure files, secret files like .env, changes of 800 lines or more, deletions of 300 lines or more, and whether any tests were added.

When does the list update?

After every finished turn of every agent.

Related features

All featuresSee the 18 supported coding agents

Bring your agents to one desk.

Start on the free plan. Download it, add a project folder and open your first agent.