Skip to content

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.

App review flowReview inside the active worktree
Worktree-scoped
01Open reviewUse Files, Diff, or Review for this worktree
02Create threadsAnchor comments to a line range or file
03Send findingsChoose the current, new, or background chat
04ContinueRead checks and use the adaptive Git action
Files, threads, agent replies, checks, and the next Git action stay attached to the same worktree.
SurfaceWhat it does
Files in the right panelLists changed files, statuses, additions, and deletions
The main Diff viewShows the worktree comparison and accepts line-range comments
Review in the right panelCollects open, pending, and resolved threads with submission controls
The review toolbarSends pending findings to the current chat, a new chat, or the background
The adaptive Git actionOffers the next valid commit, push, PR or MR, repair, merge, or cleanup action

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.

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.