Maria shapes the product. Sam runs the coding agent. Their request, “Add a Cancel plan button,” becomes a proposal that ends paid access immediately. Maria spots the assumption: the customer has already paid for the rest of the billing period.
This walkthrough continues the homepage’s cancellation example. It is an illustrative story, not a customer result.
Sam’s agent proposes
Access ends immediately.
Maria requests a change
“They’ve already paid. Keep access until their paid period ends.”
The agent revises
Access continues until the paid period ends.
Ready for Maria to review. Not yet approved.
Before starting: Sam’s repository is connected to a Pathmode workspace, and Maria has permission to review and approve the proposal.
If the repository is not connected yet
A workspace member opens repository setup, chooses the product, and gives the adoption command to the repository agent. Complete adoption before sharing the review link. Installing the MCP server alone does not connect an existing intent to the workspace.
Compare the proposal with the request
Maria opens Sam’s review link. The original request says:
Add a Cancel plan button under Settings, Billing.
The agent understood that cancellation should end access immediately. That behavior is implementable, but the request never said customers should lose time they already paid for. Maria can identify the mismatch by comparing the two, even if Pathmode has not raised a question about it.
Send the correction
Beside the proposed behavior, Maria chooses Correct it and explains the behavior she wants:
They’ve already paid. Keep access until their paid period ends.
She reviews the correction before sending it. Use this recommendation can supply suggested wording for that correction; Discuss this helps her work through the interpretation before deciding.
Sending the correction creates a change request for Sam’s repository agent. It does not update the proposal or approve implementation yet.
Review the agent’s revision
Sam asks his agent to read and apply the change request. The agent updates the repository intent and returns the revised proposal. If it cannot apply the correction, it reports why so Sam and Maria can resolve the issue.
Maria returns to What the agent changed after your correction and checks the result: access now continues until the paid period ends. The reason remains alongside the decision: The customer has already paid for access through that date.
She also checks the surrounding outcomes, scope, constraints, failure cases, and verification. The corrected sentence needs to agree with the rest of the proposal.
If the proposal changed while the correction was waiting
A request belongs to the revision Maria reviewed. If that revision has changed, review the current proposal and submit the correction again. A waiting or refused request is not an applied answer.
Settle the remaining questions
A correction can come from Maria spotting a misreading, as above, or from an open question Pathmode surfaces. For an open question, Choose recommendation selects the suggested answer, Suggest a change supplies a different one, and Leave undecided keeps the question open. These answers still go through the repository agent before becoming part of the proposal.
For this example, the remaining decisions build on the paid-access rule:
When does access end?
End of the paid period. Keep access active through the period the customer already paid for.
Settle this first. Resuming and overdue-payment behavior depend on it.
Can the customer resume?
Allow resuming before the paid period expires, without skipping or duplicating charges. After expiry, do not resume the canceled subscription.
What happens when payment is overdue?
Stop retries and renewal. Preserve any remaining paid access; end access immediately if the paid period has already expired.
These are this example’s decisions, not universal cancellation policies. Maria reviews each answer and the revision the agent returns. Keeping access also means checking that it ends at period close; the cancellation click alone does not finish that work.
If a dependent answer no longer fits
Review the recorded access-timing decision, then use Revise answer to make the dependent behavior match. Do not choose a recommendation based on an earlier answer. A choice left undecided remains unresolved and continues to block authorization.
Approve the revised proposal
When the whole proposal describes the intended behavior and the remaining review requirements are satisfied, Maria chooses Authorize implementation. This approves the exact repository revision she reviewed.
Sending a correction, answering a question, or passing a readiness check does not grant that approval. If the repository revision changes, the changed revision needs fresh authorization.
Build and check the agreed behavior
Sam’s connected agent reads the current repository intent and hosted review state, checks that the revision is authorized, and implements within its scope.
The engineer still runs checks for paid-period cancellation, resuming before and after expiry, overdue payments, and repeated requests. Receiving the right proposal does not prove that the code follows it.
Continue with Hand the authorized proposal to your coding agent for Sam’s side of the handoff.
Use the reasoning in a later coding session
Later, Sam asks his coding agent:
Clean up canceled accounts.
In this example, the connected agent reads the earlier decision and its reason before proposing the cleanup. It responds:
I’ll keep accounts with paid access until their billing period ends, following Maria’s decision.
Deleting those accounts now would cut off time the customer already paid for. Sam did not repeat the cancellation rule, but the saved reason explains why it still matters.
The earlier approval covers the cancellation revision. It does not automatically approve a new cleanup proposal. Sam and Maria still review and approve that proposal before building it.
For setup from the beginning, follow Your First Intent in Pathmode.
Review your agent’s proposal with your team.
Compare it with your original request, correct the behavior, and approve the revised proposal before implementation.
Review with your team