# Code changes

Review captured changes with the original lines and context intact.



 Old async function submit() {
  await save(project);
}

 New async function submit() {
 + if (pending) return; 
  await save(project);
}

“What happens after a failed request?”

Select the relevant lines on either side. Illustration of a code review.



## Read the patch

Switch between **Unified** for a single change stream and **Side-by-side** to compare modifications directly against previous code. Collapse files as you complete them and mark them viewed to maintain your place.

Highlight the relevant lines on either the old or new side, then ask for a concrete adjustment:

> After a failed request, can I submit again? The button should become usable.

## Review the next round

Every diff publication is a complete, self-contained patch snapshot. When your agent publishes a revised patch, click its linked lines or open the latest version to inspect the fix.

You can unfold code context within the captured bounds. If you need to see more surrounding lines than were originally captured, ask your agent to republish with wider context—r3 stays isolated and never reads your live disk checkout directly.