Review & publish
Approve the plan before files change, read the diff before it merges, and publish a branch with a pull request in one step.
Proliferate gives agent work up to two checkpoints. When a session runs in a plan mode, the first is the plan, before any files change — it lives on the agent, so approve or reject it from the plan card in the transcript (see plan mode and plan approval). The diff checkpoint always applies: read the changes before they merge, and that's what this page covers.
The Changes panel
Every workspace has a Changes panel that shows the current diff against a base you pick. The scope selector switches between Unstaged, Staged, Branch, and Last turn, each with its own changed-file count.
- Per-file stage and unstage, with an aggregate additions/deletions count in the header.
- Hunk-level stage, unstage, and revert pills inside a diff, in the unstaged and staged scopes.
- Collapse or expand all diffs, toggle word wrap, and refresh from the panel's options menu.
- Last turn scope with a one-action undo that reverses the last agent turn's file changes together, for when a turn went the wrong way.
Get a second opinion
You don't need a separate reviewer product to get another set of eyes. Because parallel agents can read the same workspace, ask your agent to spawn a delegated session with a review job instead of an implementation job:
The delegated session shows up as a normal row in the transcript that you can expand to see who it is and what it was asked to check. Change the prompt to change the lens — a security pass, a test-coverage pass, or a "does this match our existing patterns" pass.
Publish
When the diff is ready to leave the workspace, Publish pushes the branch and can open a pull request in the same step. The dialog shows the changed files, a commit message, and — for a pull request — a title, description, base branch, and a draft toggle.
Publishing pushes real commits to your remote. Read the diff in the Changes panel first, especially for cloud workspaces you haven't been watching closely.
Once a branch has a PR, its status shows as a pull-request glyph next to the
workspace in the sidebar, with a tooltip like PR #805 · Open · Checks failing.
The state is one of Open, Draft, Merged, or Closed; open and draft PRs also
surface checks (failing or pending), whether changes were requested, and
approval. Ahead/behind counts (↑2 ↓1) show when the branch has diverged from
its base, and a merge conflict tints the glyph. PR status refreshes when a turn
ends rather than on a timer, so a snapshot reads as of {time} when it may be
stale.