Skip to main content
Review the changed code and its evidence before accepting an agent’s result. Dure opens that review in a separate diff window you can keep beside the conversation.

​
Open the correct worktree

In the local agent’s pane toolbar, click the diff icon. Its tooltip reads View diff in a new window, and when the branch has changes it shows counters such as C2 W1 for committed and uncommitted files. The review opens in a separate window. The comparison uses the branch’s fork point and includes uncommitted changes and new files. Select a changed file and read its diff. Opening the review does not stage or commit anything.

Compare the original and modified search function side by side.

​
Send actionable feedback

  1. Add a comment to a file or diff line.
  2. Describe what should change and why, with the expected behavior where useful.
  3. Send the pending comments to the linked agent.
  4. Check the send result, then review the next revision.
A review without a linked agent can still be read. Sending requires a known recipient; an error does not mean the feedback arrived.

An unsent comment asks for a mixed-case search test and preserved empty-query behavior.

​
Verify and combine

Ask which checks ran, inspect their results and try the affected behavior. Review the updated diff before committing or combining branches with your normal Git workflow. Separate worktrees can still conflict; check the combined result too. Keep a Diff or source-control window beside your agents or on another monitor. The built-in Diff review is for local worktrees. For SSH projects, inspect changes using Git on the remote host. For work that started from an issue or pull request, return to GitHub to review its current status.