Keep your team’s decisions
in this build and the next.
Shape your product without running the coding agent. Review its proposal together, resolve what needs to change, and approve the revised plan. The agreed decisions carry into implementation, and the reasoning stays available for later work.
For teams where the people who decide what to build are not the ones running the coding agent. A team of two, or a whole product team.
For engineers: Install Pathmode free
“Add a Cancel plan button.”
ExampleThe agent’s proposal
When a customer cancels, access ends immediately.
“They’ve already paid. Keep access until their paid period ends.”
Maria’s correction · from the review link
One piece of customer knowledge. A different product decision.
Works with Claude Code · Codex · Cursor
01 · Review
Did the agent understand what you meant?
Keep the brief in your ticket, doc, or thread. Your engineer gives it to their coding agent, which proposes the change from the repository and attaches your request word for word. You compare the two in Pathmode and say what will happen to a customer and what you are deciding, without knowing how the software works. You do not write the spec again or operate Git.
Spot something that needs correcting, or answer a question the proposal leaves open. Either way the agent gets a decision to apply before you approve the revised plan.
- Use this recommendation: Open a correction with the suggested wording, ready for you to review and send.
- Correct it: Say what should happen instead.
- Discuss this: Talk the interpretation through before choosing a correction.
- What you asked for
- Add a Cancel plan button under Settings, Billing.
- The agent understood
- Add the button. On click, cancel the subscription and end access immediately for the customer.
- The choice to settle
- When someone cancels, does access end immediately or at the end of the period they paid for?
- Pathmode recommends
- At the end of the paid period.Trade-off: Cancellation may not change access until the current billing period ends.
- Your decision
- End of the paid period.
Choosing an answer sends nothing yet. The correction goes to the agent in the next step.
02 · Correct
Send the correction back to the agent.
Your answer becomes a change request tied to the version you reviewed. It tells the agent what to change and why. Sending it authorizes nothing. Your engineer has the agent apply it beside the code, and the revised proposal comes back to you.
If the proposal changed after you answered, your request can no longer be applied. Pathmode marks the next step as yours, and you answer again on the current version. An older correction never overwrites a newer decision.
- Maria’s correction
- “They’ve already paid. Keep access until their paid period ends.”
- Why
- The customer has already paid for access through that date.
- Status
- Sent to the agent. Nothing is approved yet.
Revised proposal · revision 2
Access ends immediately.
Access continues until the paid period ends.
The customer has already paid for access through that date.
Approved by Maria · revision 2
03 · Approve
Approve the revised proposal.
Review what the agent changed, then choose “Authorize implementation”. That is the button that approves the revised proposal for building. Pathmode records who approved it, when, and which version they reviewed. Sending a correction or confirming one behavior does not approve the whole proposal.
- A yes applies to one exact version: Approval is recorded against the version you reviewed. If the proposal changes afterwards, it needs your approval again, and the agent is told to wait.
- The decision stays in your repository: The approved intent.md sits beside the code it governs, in an open format. Your corrections go through the agent. Nothing edits the file behind the scenes.
- Customer material stays private: The repository gets the decision and safe references. Research, tickets, and the reasoning behind them stay in the connected workspace.
04 · Build and check
Check the build against the decision.
Your engineer’s agent builds from the approved revision. With GitHub connected and the pull request linked to the intent, Pathmode reviews the diff before merge and checks the merged changes afterwards. Claude Code plus the GitHub PR webhook is the supported path.
- Check the agreed behavior: The reviews compare the implementation with the spec. Before merge, a person can accept, reject, or waive findings. The reviews are advisory; Pathmode does not itself block a merge or stop the agent.
- Findings come back: When the build contradicts the spec, the agent can record a finding for the team to judge.
- Approval stays separate: An unapproved proposal never gets a green light from Pathmode. A passing diff check does not approve it or record your acceptance of the shipped result.
- Decision to check against
- Access continues until the paid period ends.
- Implementation to inspect
- The linked pull request’s diff before merge, then the merged changes.
This example shows what to compare. It does not represent a completed build or a passing check.
05 · Keep the reasoning
The next request can use what you already decided.
Maria approved keeping paid access until the period ends. Later, Sam asks his coding agent to clean up canceled accounts. Reading the saved decision and its reason gives the agent the context to preserve that access.
The earlier approval covers the cancellation revision. A new cleanup proposal still needs its own review and approval.
Follow the complete review →- Maria’s earlier decision
- Keep access through the paid period.
- Why
- The customer has already paid for access through that date.
- Sam’s new request
- “Clean up canceled accounts.”
- The agent uses the decision
- “I’ll keep accounts with paid access until their billing period ends, following Maria’s decision.”
Evidence, when you have it.
A proposal with no evidence still reaches review and approval. When you have customer research, support tickets, or metrics, attach them to explain the decision. Private material stays in the connected workspace, and the repository gets the decision and safe references. A pasted request is source material, not proof that the proposed behavior is right.
How designers and researchers bring evidence into the review →Give the next build the decisions you make today.
Keep your ticket and your coding tools. Review the proposal together, approve what the agent builds from, and keep the decision and its reason for the work that follows.
For engineers: Install Pathmode free. No account or API key required for the local workflow.