---
title: "How changes reach your pull request"
description: "What happens to your pull request as you keep editing: every agent reply and every undo lands on its branch by itself."
url: https://help.modeinspect.com/en/articles/47-how-changes-reach-your-pull-request
collection: "Share and review"
updated: 2026-10-29
language: en
---

# How changes reach your pull request

What happens to your pull request as you keep editing: every agent reply and every undo lands on its branch by itself.

Once a canvas has a pull request, you do not sync again. Each time the agent finishes a change in Build Mode, that change is committed to the pull request's branch, and the description is updated to cover it. Your engineers always see the latest state.

## How it fits

A canvas has one pull request and one branch. [Create a pull request](https://help.modeinspect.com/en/articles/46-create-a-pull-request.md) opens it from the changes made so far. After that the GitHub button in the canvas header shows a green dot. Clicking it opens the **Github Sync** popover with the line "Your canvas is synced with its branch", the pull request's title and branch, and **View on Github**.

Every agent reply that changed code becomes one commit on that branch, as soon as the reply is done. The commit message is written from the agent's summary of the change. The pull request description is rewritten to cover all the changes together, so a reviewer who opens it late still gets the whole picture.

Undo and Redo in the Build Mode header go to the branch too. Before either one, a dialog asks **Rewrite the open pull request?**, and after **Continue** the branch gets a commit named "Undo / Redo recent changes".

To change the title or description by hand, click the pull request's card in the popover. **Edit Pull Request** opens with both fields. **Summarize Updates** adds a paragraph about what changed since the description was last written, and **Update** saves it to GitHub.

## What it does not do

-   It does not merge. Merging, requesting reviews, and closing happen in GitHub, by your engineers.
    
-   It does not sync canvas edits. Frames, captures, and comments on the canvas stay in Modeinspect. Only code the agent wrote reaches the branch.
    
-   It does not keep syncing after the merge. A merged or closed pull request is final, see [Keep working after your pull request is merged](https://help.modeinspect.com/en/articles/44-after-the-pull-request-is-merged.md).
    
-   It does not open the pull request as a draft. Your engineers see a normal pull request.
    

## Next

-   [Keep working after your pull request is merged](https://help.modeinspect.com/en/articles/44-after-the-pull-request-is-merged.md)
    
-   [See the code the agent changed](https://help.modeinspect.com/en/articles/49-view-code-changes.md)
    
-   [Create a pull request](https://help.modeinspect.com/en/articles/46-create-a-pull-request.md)

## Related

- [See the code the agent changed](https://help.modeinspect.com/en/articles/49-see-the-code-the-agent-changed.md)
- [Create a pull request](https://help.modeinspect.com/en/articles/46-create-a-pull-request.md)
- [Keep working after your pull request is merged](https://help.modeinspect.com/en/articles/44-keep-working-after-your-pull-request-is-merged.md)
- [Create a preview link](https://help.modeinspect.com/en/articles/45-create-a-preview-link.md)
- [Share a link to the page you are on](https://help.modeinspect.com/en/articles/48-share-a-link-to-the-page-you-are-on.md)