Review and ship
Review stays attached to the worktree that produced the change. Its files, diff, comment threads, agent replies, checks, pull-request state, and next Git action all refer to the same branch and target.
Where review lives
Section titled “Where review lives”| Surface | What it does |
|---|---|
| Files in the right panel | Lists changed files, statuses, additions, and deletions |
| The main Diff view | Shows the worktree comparison and accepts line-range comments |
| Review in the right panel | Collects open, pending, and resolved threads with submission controls |
| The review toolbar | Sends pending findings to the current chat, a new chat, or the background |
| The adaptive Git action | Offers the next valid commit, push, PR or MR, repair, merge, or cleanup action |
Send findings to an agent
Section titled “Send findings to an agent”Select pending threads and choose a destination. Current chat stages them in the active conversation. Open in new chat starts a separate Chat UI session. Run in background dispatches the same review bundle without replacing the visible tab.
Agent replies return to the related threads, and code changes appear in the same worktree diff. Thread state remains separate from code state: resolving a thread records the decision but does not alter the files.
Continue from the updated state
Section titled “Continue from the updated state”After the agent responds, reopen the affected diff and review any updated threads. The app refreshes worktree and forge context, then changes the Git action to the next available state. Depending on that state, the action can commit and push, create a PR or MR, dispatch blocker repair, mark a review ready, merge, or clean up the worktree.
Choose your next topic
Section titled “Choose your next topic”- Use Review changes for comment states, agent destinations, and CLI controls.
- Use Git actions and pull requests for action priority, routing, merge strategies, and shortcuts.
- Read Worktree cleanup for deletion safeguards and teardown behavior.