Review an agent’s working changes with Paneflow Changes

The Changes tab in Paneflow shows local edits beside your agent's terminal. Compare files with the latest commit (HEAD), open them in the editor for context, or restore a block you want to remove.

The steps below describe Paneflow 0.17.5. Changes includes staged and unstaged edits and untracked files. It groups changes by checkout, regardless of who made them. If several agents share the same files, their edits appear together.

Updated guide. This article originally announced the Diff interface in Paneflow 0.3.7. It now describes the Changes tab in the dock.

Choose the checkout to review

Open your Git project, select the tab for the checkout or worktree you want to review, then open Changes in the dock. Check the file paths before reading the diff.

The comparison shows the current files against HEAD. Staged and unstaged edits are combined in that view. To see exactly what your next commit will contain, inspect the Git index separately with git diff --cached.

Changes excludes edits already committed on the branch. In a repository without a first commit, it uses an empty tree as the comparison base.

Read the diff with its context

Choose Split to read the versions side by side or Unified to read additions and deletions in one view. Words highlighting marks changes within a line.

Whitespace options can trim or ignore whitespace in the comparison. Keep Default when spacing affects behavior, such as indentation in Python.

If you need the surrounding code or want to make a correction, open the file in Files, the integrated editor. Save your edits to include them in Changes, which reads files on disk.

When a file has no text diff

In Paneflow 0.17.5, Changes lists binary files, files over 512 KiB, and certain lockfiles without displaying a text diff. The list shows up to 200 files and indicates when more files are omitted.

A file without a text diff can still have changed. Use Git to inspect the full file list and a suitable tool to review large or binary files.

Restore a block with Revert

In a modified text file, Revert replaces a block with its content from HEAD. Clicking writes to disk immediately, without a confirmation dialog. Copy or otherwise preserve edits you may want to keep before using it, then check the remaining diff.

Revert leaves the Git index unchanged. If you had already staged the block, it remains in the next commit until you update the index. Check git diff --cached after restoring staged work. Revert does not delete untracked files.

Paneflow refuses restoration in these two cases:

• The file has unsaved edits in the editor. Save them or discard them if you no longer need them, then reread the diff before retrying.
• The file changed on disk since the diff was loaded. Reread the refreshed diff before retrying, especially if an agent is still editing the file.

Review the whole branch with an agent

To ask an agent for a review, start it in the checkout you intend to inspect and name the base branch. For example, if your branch is based on main:

Review this branch against main, including committed changes and local edits. Do not modify files. Report bugs and regression risks with file paths, line numbers, and relevant tests.

The agent can then examine committed changes that Changes leaves out. Read its findings alongside the code, make any needed corrections, and run the relevant tests. Before committing, inspect git diff --cached to verify what you are about to record.