- Features
- Review
Review the agent's work before anyone else sees it.
The Review tab diffs a session's worktree against its base branch, like a pull request. Comment on lines and send the comments to the agent, run an AI review, or let a review-and-fix cycle run on its own.
A pull request view of the worktree
The Review tab compares the session's worktree with its base, using the remote-tracking branch when there is one, so it matches what the pull request will show. Untracked files are included. Switch between unified and split views; in both, the words that changed inside a line are marked. The file list shows each file's change type, line counts and how many comments are open or resolved on it.
Read it in the docsLive demo · simulated sessionsSessions, review tab
AI review on demand
Run AI review hands the diff to a separate, headless Claude, which looks for bugs, security issues and risky changes and leaves its findings as inline comments. You write the review instructions, globally or per workspace or project. Plexus supplies the output format, so the comments land on the right lines whatever your instructions say.
Read it in the docsLive demo · simulated sessionsSessions, review tab
Review and fix, unattended
The review-and-fix cycle runs an AI review, starts a separate headless agent to apply the fixes, waits for it, and reviews again. It stops when a review finds nothing or when it reaches the round limit, 10 by default. It asks for consent once per repository, refuses to run on the project's main checkout, and never pushes. Watch agent opens a live, read-only view of the fix agent while it works.
Read it in the docsLive demo · simulated sessionsSessions, review tab
The pull request conversation, under the diff
Once a session has a pull request on GitHub or Bitbucket, its review threads appear under the lines they are about. Comments, verdicts and outdated threads sit in a section above the diff. Reply, resolve, start a new thread, or publish one of your local notes to the pull request after a confirmation that names the repository. Send PR comments to agent hands the threads to the agent. Plexus fetches the conversation when you open the tab, focus the window or press Refresh. There is no background polling.
Read it in the docsLive demo · simulated sessionsSessions, review tab
Review a colleague's branch as well
Start a session on an existing branch, such as a colleague's branch or the head of a pull request you were asked to review, and set Compare with to the branch it will merge into. The Review tab then shows their work with the same diff, notes, AI review and pull request conversation. The session has its own worktree, so your main checkout and your other sessions stay where they are.
Read it in the docsLive demo · simulated sessionsSessions, review tab
Read more
- Review & diffs: the full Review tab, from the diff to the review-and-fix cycle
- Pull requests: opening pull requests and tracking their status
- Settings: review instructions, models and the round limit
Questions,
Do my review notes leave my machine?
No. Notes are stored locally and exist so the agent can read them. A note reaches GitHub or Bitbucket only when you publish it to the pull request, after a confirmation that shows the text and the repository.
Does the review-and-fix cycle push my code?
No. Plexus never pushes for you. The cycle edits files in the session's worktree, and you read the result before it goes anywhere.
What runs the AI review?
A headless Claude Code instance on your machine, using your own Claude Code login. You choose the model and effort level for the review and for the fix agent in Settings → Git.
Which pull requests can I review in Plexus?
Pull requests on GitHub and Bitbucket, opened from a branch in the repository itself. Pull requests from forks are not supported yet. Bitbucket has no review verdicts, so its review comments arrive as ordinary threads.
Run your agents
Plexus is free to download for macOS, Windows and Linux. It runs the Claude Code you already have, with your existing login.
Comments the agent reads
Hover a line, write a note and add it. Notes stay on your machine. When you are done, Send N comments to agent turns every open note into one prompt and writes it to the running agent, which picks it up on its next turn. Sent notes are marked resolved, so the file list keeps a record of what you handed over.
Read it in the docsLive demo · simulated sessionsSessions, review tab