# Review

Review runs a **separate agent session** from your main workspace chat. It is optimized for **reading and critiquing changes** against the base branch, without mixing that conversation with the implementation thread where you asked the agent to write code.

## How it differs from the main feed

- **Main (Activity)** — Where you assign work, iterate on fixes, and drive the agent forward.
- **Review** — A dedicated channel with its own message history and model defaults. When you start a review, Polyscope opens the Review tab and sends a structured review prompt so the agent focuses on the diff, project instruction files, and high-signal issues.

Stopping or clearing the review conversation does not clear the main channel, and vice versa.

## Starting a review

1. Select a workspace.
2. Click **Review** in the header (next to merge / run script actions), or press **⌘⇧E** (the default binding).
3. Optional: use the chevron next to **Review** to pick a **specific model** for this run. That choice is remembered for the review channel.

The first time you start a review for a workspace, the **Review** tab appears beside **Activity**. Switch between tabs to read review output versus ongoing implementation chat.

## What the reviewer is asked to do

Polyscope sends built-in **Code Review Instructions** that tell the agent to:

- Use **`GetWorkspaceDiff`** to inspect changes against the base branch (summary stats first, then full or per-file diffs as needed).
- Load relevant **`AGENTS.md`** and **`CLAUDE.md`** files that apply to changed paths, and check compliance only where those files actually scope the edits.
- If a pull request is linked, use **`gh`** for PR **title and description** for context — but **review the workspace diff**, not the GitHub PR diff.
- Prefer **validated, high-signal** findings (bugs, security, clear instruction violations) and avoid noise (style-only nits, speculation, pre-existing issues outside the change).

You can tailor behavior further with **Review Preference** and **Review Model** in repository settings (see [Repositories](/docs/core-concepts/repositories)).

## Repository and global settings

Per repository, under **Settings → Prompts**:

- **Review Preference** — Optional text appended to the built-in instructions as `User Preference`. Use it for team conventions (e.g. “always check migrations,” “focus on API compatibility”). Leave unset to use only the built-in instructions (plus any **global** preference you have configured).
- **Review Model** — Default model for review for workspaces in this repo. You can still override per run from the header menu.

Global defaults apply when a repository does not override them.

## Closing the Review tab

Close the **Review** tab from the tab bar when you are done. If a review is still running, Polyscope prompts you or stops the agent first, depending on context. You can middle-click the tab to dismiss when supported.

## Review vs Opinions

| | **Review** | **Opinions** |
| --- | --- | --- |
| **Goal** | Structured pass over **your workspace diff** with one focused review thread | **Multiple models** answer the same question, then **synthesize** a consensus |
| **Best for** | “Ship-quality” feedback on a concrete change set | Comparing perspectives before a big decision |

Use [Opinions](/docs/digging-deeper/opinions) when you want several models in parallel on an open question; use **Review** when you want a dedicated review pass on what changed in the workspace.