See what needs review
See your agents’ worktrees and their uncommitted changes in one place. Review the risky changes, investigate anything that needs fixing, and commit your code from the Changes page.
This guide uses Panolayer’s Twitter example, twitter-starter. If you’ve followed Fix your first bug with Panolayer, use these steps to review the deletion fix.
The screenshots and short videos show several changes in the same Twitter app, including formatting, search, export, and saved-post changes. Your file list, risk scores, and commit IDs will depend on the work you’re reviewing. Click a screenshot to inspect it at full size.
Open Changes in the sidebar. On the right-hand side, you can see the different worktrees and the uncommitted code from your agents. Select a worktree to see what that agent changed, with files scored from highest to lowest risk.
Move between your agents’ worktrees, review their changes, and commit code from this page. The risk scores make it quick to see which files need your attention and may need a fix.
You can also select an existing commit in History to review what was recorded. If you already merged the deletion fix, find it there; its merge has already recorded the change locally.
Review changes from highest to lowest risk
Changes scores files from risky to not risky and explains what changed. Start with the highest-risk files to understand what needs review and potentially fixing before you commit.
Switch between Risk Spectrum, Risk Bars, and Overlap to explore the same changes in three visual views.
Risk Spectrum
See the changed files arranged along a horizontal spectrum, from high risk on the left to low risk on the right.
Risk Bars
Compare files as bars ordered by risk. The view runs from very risky to not risky, making it easy to see where the changes need attention.
Overlap
See where UI changes, logic changes, and risky changes overlap. The grouped files show how these parts of the change relate to one another.
Inspect a change that needs attention
The risk overview shows where to focus your review. Open a file when you want to understand a specific change in more detail.
- Select a file in the graph or changed-file list.
- Read its path, change summary, and risk explanation.
- Choose Split for a side-by-side comparison, or Inline to read the changes in one view.
- Follow the change through the relevant function and its callers. Check related tests, configuration, and dependency files too.
For the deletion fix, open components/Post.tsx and inspect handleDelete(). Check how the change addresses the reported canDelete condition, and whether user confirmation, the deletion request, and successful-response handling still make sense together.
Read the analysis and ask about concerns
Deep analysis from Panolayer Agent is always available in Changes. Open the Panolayer Agent – Deep Analysis panel to read its assessment, concerns, and source references. Follow a concern into the relevant file to understand what needs attention.
Watch: Inspect analysis of a Twitter export change
The existing analysis clip shows an export change in the Twitter app, with concerns connected to the affected files.
Use Chat to continue the review with Panolayer Agent. Ask a question tied to the behavior you’re checking, such as:
“How does this change fix the deletion issue, and which tests cover the expected behavior?”
Use the answer to navigate the change and investigate anything unclear.
Read verification alongside the review
Changes can show verification results on the affected functions. Read failed rules and any checks that are still pending or unavailable, then follow their explanations into the code.
The risk overview helps you choose where to look. Deep analysis gives you concerns to investigate. Verification reports checks against expectations about code behavior. Read them together with the diff and relevant tests.
For the deletion example, confirm that the selected failure was repaired and review any new failures separately from pre-existing issues. See Understand a verification result for the summary fields and statuses.
Run the application when the change needs a runtime check. For this fix, try deleting a post and check that confirming or cancelling behaves as expected.
Merge the agent’s work when you’re satisfied
When the agent requests a merge, review the verification summary and confirm the target branch. Choose Not now to keep reviewing, or Merge into main to bring the work into the sample’s main branch.
The Merged into main confirmation shows the commit ID. This workflow records the agent’s change in local Git history; you do not need to commit that same change again.
Commit any uncommitted edits
Use this step for your own edits or other uncommitted work in the current workspace. If the agent’s merge already saved the change and you have no further edits, continue to History.
- Check the full changed-file list.
- Review the suggested commit message. Use Edit message if it needs to describe the change more clearly.
- Choose Commit to save the changes to the local branch. Choose Commit & Push if you also want to send the commit to a configured remote.
A Panolayer commit includes every changed file in the workspace. Use Git directly if you need to stage only part of the change. Read any reported check failures before deciding to commit; a commit can still be created when checks fail.
Confirm the result in History
Open History and find the new commit using its message, author, and commit ID. Select it to inspect the recorded change, then return to Working tree to check for remaining uncommitted edits.
Watch: Confirm a Twitter saved-post change in merge confirmation and History
This existing clip follows a saved-post change in the Twitter app. Use the commit ID from your own merge confirmation to find your change.
For the deletion fix, you should be able to find its recorded change and inspect the files that landed. Check that no unexpected uncommitted edits remain.
Push when you’re ready to share the commit
A merge or commit saves work locally. To send an existing local commit to your Git remote, open Git and choose Push.
Pushing requires a configured remote and permission to write to it. If the sample has no remote, the local commit completes this walkthrough. If a push reports an error, read it and resolve the remote or sign-in problem before trying again.
Use your Git host for pull requests and team review.