How a review works · for coding agent operators
Hand off the review.
Keep the terminal.
Your agent proposes the change. A colleague answers its questions and checks the proposal. Once that version is approved, your agent can build it.
A background listener reports answers and approval to your agent. Your reviewer works from a link.
M Maria · product · review link
Your turn · 2 questions
1. When should access end?
2. Should the customer get a confirmation email?
S Sam · engineering · terminal
npx @pathmode/mcp-server watch-review --build
Listening in the background for Maria’s answers.
One review, from both sides
See what happens
on both sides.
Sam runs the coding agent. Maria knows the customer and reviews from a link. Here is what each of them sees at four moments of one review. This example assumes Sam asked the agent to build after approval.
Maria · product · review link
Your turn · check version 3
Let customers cancel their plan themselves
What customers would experience
- After cancelling, the customer keeps access until the end of the paid period.Added from your answer
- A confirmation email states the exact date access ends.Added from your answer
Does this match what you meant?
Watch the example: two answers become two proposal lines. Maria checks those lines before deciding whether to approve.
Sam · engineering · coding agent
From answers to an updated proposal.
Maria sends both answers together. The agent writes them into the proposal, then waits for Maria’s approval.
Show full terminal output
PATHMODE_REVIEW_READY: 2 change requests from review to apply (cr_7d1e, cr_7d1f). Run get_agent_prompt for this intent with mode "draft", then apply each one with intent_save using its exact changeRequestId and baseRepoBodyRevision, or reject it with a concrete reason. Then run "npx @pathmode/mcp-server watch-review" in the background again.
Send your colleague the reviewer guide →
Your first review
Connect. Invite. Listen.
01
Connect your agent and repository.
Install Pathmode for your coding agent, then use repository setup to connect this repository to a workspace. Setup provides the connection command and key.
/plugin marketplace add pathmodeio/claude-plugin /plugin install pathmode@pathmodeInstalls the Pathmode plugin and MCP server for Claude Code.
02
Prepare the proposal and invite your reviewer.
Ask your agent to save the proposal to the workspace, attach your original request, and list the questions that need your colleague's judgment. Start with today's problem. Give each option a reason and consequence, with the supporting source and proposed line as context for that question.
Prepare this change for review. Describe what customers will experience and ask the questions you need answered before building. Attach my original request exactly as written.
Open the proposal and invite your colleague as an editor so they can answer questions and approve. Viewers can read. Your reviewer needs no API key or terminal.
The reviewer answers the available questions and uses Send answers in the bottom bar. Once the agent has written those answers into the proposal, the reviewer checks the customer behavior and uses the version-specific approval action. Sending answers gives no permission to build.
03
Have your agent start the listener.
If your request includes implementation, ask your agent to run this in the background from the repository root:
bashnpx @pathmode/mcp-server watch-review --buildUse
--no-buildfor a proposal-only request. The agent will ask you before building, even after approval. The reviewer sees which applies before deciding.Automatic continuation depends on your coding client waking the agent when a background command finishes. If it does not, bring the listener's result back to the agent to continue.
What approval allows
One specific version
The agent must check the current approval before building. Any edit to the proposal needs a new review and approval.
Readiness still matters
Open questions and requests for changes block approval. Approval also leaves execution checks in force; the agent must stop and report any blockers.
Release is a separate decision
Approval permits implementation. It does not release the change to customers. Your team keeps its release process.
If implementation reveals that an assumption is wrong, the agent records the finding and brings the proposed correction back for review.
When you need the details
The listener stopped. How do I continue?
One run listens for up to 30 minutes. If no answers arrive, the agent starts the next run itself. All runs for one review share four hours of listening time, counted from the first start, and restarting does not add more. When the four hours are used up, the agent stops and tells you. Ask it to listen again with --renew, adding --build if you requested implementation. That opens another four hours.
npx @pathmode/mcp-server watch-review --renew --buildTo change the build declaration while a listener is running, use --build --declare or --no-build --declare on the watch-review command.
How are answers and requests for changes handled?
The reviewer sends answers together. The agent handles each answer separately, and it stays marked as sent until written into the proposal. Sending them does not approve the proposal. Unapplied answers become available again after the ten-minute lease. An answer rejected with a reason needs clarification; earlier words and completed answers are kept.
The agent reads requests with get_review_feedback and responds with respond_review_feedback. The reviewer decides whether a response addresses their request; an open request blocks approval.
What does the agent check before building?
Read the current intent with get_intent, confirm approval covers its current revision, then request get_agent_prompt in execute mode. If execution checks fail, report the blockers and stop. A copied prompt needs a fresh check of the current review state before continuing.
For tools and error codes, use the developer reference. For the full walkthrough, read Wire Pathmode into your coding agent.