# From diff to merged, without leaving the tab

> AQ shows exactly what an agent changed, lets you comment on any line, runs an independent review, and merges only when checks pass and the review is current.

Published October 28, 2026 · by the AQ team · Canonical: https://aq.dev/product/review/

See exactly what the agent changed this turn, comment on a line, get an independent review, and merge when the checks pass and the review matches the latest commit.

Reviewing an agent's work in AQ happens next to the conversation that produced it. The Changes panel shows the diff in the scope you choose, a comment on any line goes to the agent with your next message, a review thread on another model reads the same diff, and the pull request card merges only when it is safe to.

## Four ways to look at a change

This turn

### What just happened

Only the files the agent touched in its last turn, even if you pulled or rebased since.

Uncommitted, Branch

### The work so far

Everything not committed yet, or the whole branch against its base.

One commit

### Step by step

Read a single commit when the history tells the story.

## Comments that reach the agent

Click a line and write a comment. It rides your next message to the agent as "at path:line: your words", or goes on its own. Files you have read get a tick, and file links in the agent's replies open the diff at that file instead of a dead link.

The pull request card: checks, review state, and Fix with this thread, Re-review or Merge.

## A merge that explains itself

Merge squashes the pull request on GitHub. It refuses, in words, while checks are pending or failing, while the head commit is unknown, or while the last review is older than the latest commit. Re-review runs the review again on the current head; Fix with this thread hands the failing checks back to the agent.

## Independent review and security scans

Start a review from the Changes panel and a read-only review thread reads the diff and pins its findings to the lines. Crews prefer a reviewer on another vendor and account when available (see [Crews](https://aq.dev/product/crews/)). For security, scan the diff, the branch or the whole codebase with Hinoki, a security model, and get findings with severity, evidence and a fix. Previews add a third view: pin a comment on the running app itself (see [previews and comments](https://aq.dev/docs/previews-and-comments/)).

Review where the work happens, with the app running beside it.

[Start free](https://aq.dev/signin?mode=build)[See pricing](https://aq.dev/pricing/)

## Frequently asked questions

### How do I review code written by an AI coding agent?

Read the diff for the agent's last turn, comment on the lines you want changed, run an independent review on another model, check the running preview, and merge only when the checks pass. AQ puts all of that in the work item's tab.

### Why would AQ refuse to merge?

When checks are pending or failing, when the head commit is unknown, or when the last review was done on an older commit than the one you would merge. The reason is shown in words.

### Can teammates outside the repository review the work?

Yes. Share the live preview with a guest link on the Pro plan; reviewers comment on the running app and their comments can be sent to the agent as its next prompt.

---

About AQ: AQ is the multiplayer coding harness where teams chat, build and run bots with every AI coding agent, like Claude Code and Codex: shared live terminals, review and merge, app previews and standing jobs, in your own cloud. Start at [aq.dev](https://aq.dev/).