Changes and review

Code review lives inside the task that changed the files, with exact patches, gates, browser evidence, and Accept or Discard.

Open beta guideJump to first section

Exact task changes

The Changes section reads the task's captured worktree diff: file status, additions and deletions, and capped patches with an honest “too large to preview” state. It also includes frames and task-linked design events when relevant.

Verification

Project checks run before acceptance and render as gate chips. Iterel's verify browser is limited to the task's loopback dev server; actions stream into the run and screenshots stay on the machine that performed them. Other clients see the verification badge even when the machine-local thumbnail is unavailable.

Resolve the review

Accept commits pending edits and merges the per-task worktree into the base branch. Discard removes the isolated worktree and persisted review result. In-place runs carry stronger warnings because they cannot promise the same cleanup boundary.

Contextual workbench

A task-scoped single-file workbench is available as a post-MVP convenience for quick edits and checks. It is not a Code mode or a project-wide IDE; full authoring remains in the editor you already use.