Code Review

The Code Review panel lets you review, edit, and manage Git diffs in real time, with options to attach, revert, or open files directly.

Overview

When you are working locally in a Git repository with uncommitted changes, the Code Review panel lets you inspect, edit, and manage code changes directly inside Warp. It integrates with Git and Warp's Agents, giving you the ability to:

• Review diffs and attach them as context for the Agent

• Apply, edit, or revert changes in real time

• See changes made outside of Warp or by Warp's Agents automatically reflected

Any uncommitted changes appear in the panel (or compare the changes on your branch against main or master ). Switching branches or saving files updates the panel instantly, so it always reflects the current state of your codebase.

Code Review Demo

Full view of Code Review panel and terminal pane.

To review agent-generated diffs, leave inline comments, batch your feedback, and have the agent apply all requested changes, see Interactive Code Review.

Opening the Code Review panel

The Code Review panel can be opened in several ways. Each entry point makes it easy to inspect and manage changes without leaving your workflow.

You can also open the Code Review panel with CMD – SHIFT – + on macOS or CTRL – SHIFT – + on Windows and Linux.

1. Universal Input: Git diff chip

In the Universal Input editor, when you’re in a Git repository with changes, the chip shows the number of files modified along with lines added and removed. Clicking the chip opens the Code Review panel with the relevant diffs.

2. Agent Conversation: Review Changes Button

When an Agent makes code edits in an Agent Conversations, a Review changes button appears at the bottom of the conversation. Clicking it opens the code review panel.

Review changes at bottom of Agent Conversation.

3. Agent Conversation: Toolbelt (Bottom Right)

During an Agent conversation, you can view all changed files in the toolbelt chips at the persistent bottom right. From there, you can open the Code Review panel directly.

4. Warp Tab Bar

In any Git-tracked repository, you can open the Code Review panel by clicking the plus/minus icon in the top-right corner of Warp, next to your avatar.

Viewing All Edited Files

Inside the Code Review panel, you can open the file sidebar to browse all changed files in your repository. Clicking on a file will automatically scroll to that file in the panel.

Viewing all edited files in the code review panel, with the file sidebar open.

By default, the Code Review panel opens as a pane on the right, but you can drag it to reposition wherever you prefer.

Reviewing diffs

By default, the Code Review panel shows all uncommitted changes on your current branch, excluding changes to files ignored by .gitignore.

Warp offers two ways to review changes:

1. Uncommitted changes: view all edits you've made locally on the current branch.

2. Changes vs. main: compare your branch against main or master to see what would be included in a pull request to that branch, for instance.

   1. Warp automatically detects the target branch and updates the comparison accordingly.

3. Changes vs. another branch: compare your work against any arbitrary branch for stacked PRs, feature comparisons, or alternate base branches.

You can manually switch between the two views either in the Code Review panel or via the unviersal input chip:

Changing diff view in the Code Review Panel.

Changing diff view in the Universal input.

Changing diff view against an arbitrary branch.

Any saved edits made outside of Warp (e.g. in another editor), as well as changes applied by Warp's Agents, appear automatically. The panel updates in real time, ensuring it always reflects the current state of your working file and directory.

Attaching diffs as context

The Code Review pane makes it simple to share changes with the Agent. You can attach an entire diff to a prompt so the Agent has full visibility into what was added or removed.

Attaching a diff as context from the Code Review panel.

This ensures responses are grounded in your latest edits, whether you’re asking for feedback, explanations, or follow-up changes. For more details, see Selection as Context.

Reverting diffs

The Code Review panel lets you easily undo changes at different levels. In the gutter next to each diff, you’ll see an option to revert a hunk: roll back a specific set of changes (a “diff hunk”) within a file. This removes the added or modified lines and restores the previous version.

When you revert, the changes are immediately updated in your working directory. The file is restored to match the selected version, so you can continue editing or commit without the reverted code.

Opening Files from Code Review

In addition to reviewing and editing diffs directly in the Code Review pane, you can open a file directly in Warp’s Code Editor. Each file listed in the Code Review pane includes an expand button in the top-right corner of its diff view.

• Clicking the expand button (right-most button on the header) opens the file in a new editor tab, allowing you to see the full file beyond just the changed lines.

  • This is useful when you need additional context around a diff, want to make broader edits, or prefer working in the full editor rather than inline.

• Once opened, the file behaves like any other editor tab: you can scroll, edit, search, and save.

• Any changes made in the editor automatically sync back into the Code Review pane, so the diff view always stays current.

Note: from this code review file header, you can also attach a file diff as context into Warp's agent, or discard all the changes on a single file.

Directly editing code diffs

Alternatively, from the Code Review panel, you are able to click and edit the diffs directly:

Discarding all changes

The Code Review panel also lets you discard every uncommitted change on your branch in one action. Clicking Discard all removes all local modifications shown in the panel and restores each file to its state on the base branch. This is useful when you want to reset your working directory, abandon a set of edits, or start a new iteration from a clean slate.

Discarding changes will ask you confirm, but still make sure you’ve saved or backed up anything you want to keep before using it.