Review changes and pull requests
A task is not ready just because the agent has stopped working. Inspect the changes, verify the behavior, then decide how to deliver them. A local change does not need a pull request unless your workflow requires one.
Inspect the diff
Select the conversation that worked on the task, then open + → Git Changes. The panel belongs to that conversation's environment; see Select the right conversation.
Select a changed file in the list to open its diff. Use the two view buttons at the top right of the diff viewer to switch layouts:
| Mode | Button | What it shows |
|---|---|---|
| Unified | Left button, with a single column of lines | Removed and added lines together in one view. |
| Split | Right button, with two columns of lines | The before version on the left and the after version on the right, side by side. |
Removed lines are highlighted in red; added lines are highlighted in green. Use Unified to read a change in one column, or Split to compare the two versions side by side.
Compare the diff with your original request:
- Does it solve the problem or implement the expected behavior?
- Are the changes limited to the intended files and scope?
- Were tests weakened, unrelated behavior changed, or necessary edge cases missed?
Use + → Files to read the surrounding code. Ask the agent to explain an unexpected change before accepting it.
Verify the behavior
Read the commands the agent ran and their output. Use + → Terminal to run relevant tests yourself, or inspect background command output if the checks are still running.
Confirm that the original failure is resolved and that relevant tests pass. If verification is blocked by missing dependencies, credentials, or services, record that limitation and resolve it before treating the change as ready.
When you are satisfied, commit the change and deliver it according to your team's workflow. If that workflow uses pull requests, ask the agent to create one for the reviewed branch and leave it open for review. Creating or opening a PR is not the same as merging it.
Check a pull request's status
- In the upper-right corner, click the merge icon.
- The Pull requests panel lists pull request titles, numbers, and their displayed status.
- Find the PR by its title or number and read its status, such as Conflicts.
A count can appear next to the icon — for example, 2. Clicking the icon opens the list; it is not an instruction to merge a pull request.
Open a pull request in the browser
Select a pull request in the list to open its link directly in the integrated browser. The page appears as a panel tab alongside the conversation.
To review it outside Vibe, click Open in external browser to the right of the address bar and confirm with Open. See Open a page in an external browser for the dialog and external-link preference.
Opening a PR link does not grant access to its repository. For private repositories, sign in to the hosting service in the integrated browser with an account that has access. If the page is unavailable, check the URL, your sign-in, and your repository permissions.
Resolve conflicts, then review again
If a pull request displays Conflicts, identify it by number or title and ask the agent to resolve them. For example:
Resolve the merge conflicts in pull request #42. Explain how you
resolved them, run the relevant tests, and leave the changes for me
to review. Do not merge the pull request.Review the resulting changes and test results, then check the pull request's review requirements and checks before merging. Resolving conflicts is not a substitute for reviewing the code or confirming that the checks pass.
Keep or close out the work
After delivering a change, organize your conversations to keep the sidebar focused on active work. If the task used a worktree, keep it until the changes are committed and delivered or you explicitly decide to discard them. Archiving a conversation does not deliver or discard Git changes.