Use Polygraph to review the reasoning behind an AI-generated pull request.
Traditional code review tools show you diffs, so you know what has changed but not why. With Polygraph, you can ask the agent about competing solutions that were considered, scope that was cut, and surprises that came up in the session.
Each Polygraph session records the decisions that shaped the result. Previously, you'd have to sit in a call with the PR author to ask questions. Now you ask the session and get answers without a meeting.
Ask the session about the change
Section titled “Ask the session about the change”From the PR, follow the session link, or open the session directly:
polygraph session review <session-id>Review mode resumes the session with the agent answering questions instead of continuing the work. Ask anything the diff doesn't tell you. The agent answers based on the recorded session history.
What alternatives were considered, and why were they rejected?Which parts of this PR are you least confident about?What was done to address them?The agent can point at the moment in the session where a test failed, a constraint surfaced, or an approach was dropped.
What to ask
Section titled “What to ask”Questions that work well in review mode:
- Critical files: which files require attention during the review and might be buried by noise.
- Solution space: what other designs were on the table, and what ruled them out.
- Surprises: what the agent learned mid-task that the spec didn't anticipate.
- Risk: which files it touched with the least surrounding context, and what tests cover them.
- Scope: what was deliberately left out, and where that's recorded.
- Best practices: compare the work to similar sessions to see whether the PR follows them.
- Adversarial review: run an adversarial review with a different agent and summarize the findings.