Check what the AI did
Review an assistant's change on the canvas by its nodes and wires, then keep it or go back to the checkpoint you saved before the assistant started.
On this page
An assistant changed a method in your project. Before you keep the change, answer three questions from the canvas: what does it call, what does it change, and where does it stop early?
This review only gives you a way back if you committed before the assistant started. Then the assistant’s work is the only difference from that commit, and you can return to it if the change is wrong. If the assistant has already run without one, commit the project as it is now before you change anything else, so at least this point can be restored; it cannot bring back the version from before the assistant.
This page uses the enemy-stomping method from the Platformer sample, a sample from the optional Round Trip Sample - Platformer package and that you import into a test project, to practice those questions. It is an existing sample method. It is not a recorded AI edit: the captures below use a scripted stand-in, one reworded warning message inside StompEnemy, saved over a Git-committed copy of the sample. Every step names a real class, and the same steps apply when you review an assistant’s changes in any project once its folder is indexed.
The task
Section titled “The task”A generated change can build and still play the wrong game rule. In the Platformer sample, StompEnemy on PlayerController is a good review example: it starts with a guard, changes the enemy, awards score on one route, and has a second branch inside that route with a warning on each missing piece.
When this applies
Section titled “When this applies”- An AI assistant edited gameplay and you want to see what it does before you trust it.
- The change is big enough that you cannot hold the whole behavior in your head.
- You want to throw the assistant’s change away and go back to the checkpoint you saved before it started.
Review the assistant's change
Open the Graph view
Let Unity finish importing the assistant’s changes without errors, then open Tools > Round Trip > Graph view.
4 stepsFull size ↗Open the changed class
On the top rail, press the modified-classes button, the orange branch icon. Its tooltip reads Show modified classes. Choose the class the assistant touched (in the sample, PlayerController).
4 stepsFull size ↗Open the changed method and list its calls
Click the changed method in the left rail (here StompEnemy). Start at the magenta entry node and ask: What does it call? Follow the white wire and name every teal call node on it. In the sample: ChangeState on the enemy, Bounce on the motor, AddScore on the score counter, RefreshCoins on the HUD, and the two LogWarning calls that report a missing piece.
2 stepsFull size ↗Read what it changes
Ask: What does it change? Read each call node’s name and the values wired into it. The enemy’s state pin takes the Defeated pill; the motor bounces; the score grows by the stompScoreValue pill; the HUD refreshes from the Coins and Score pills. The LogWarning calls only report; they change no gameplay values.
Find where it stops early
Ask: Where does it stop early? Find every magenta EXIT node and follow its white wire back to the yellow node that leads there. In the sample, the first branch’s true output, fed by an OR of two EQUALS nodes (no enemy, or an enemy already Defeated), goes straight to EXIT. No Bounce or AddScore node should sit before it.
Keep the change, or restore the checkpoint
Compare what you found with the rule you asked for. If it matches, keep it: the change is already in the script, so there is nothing to accept.
If it is wrong, restore the intended changes from the checkpoint you made before the assistant started, using your version control client or backup. Review the whole file first: restoring a file also removes other changes made in it since that checkpoint. Let Unity import the restored script, then review the canvas again.
3 stepsFull size ↗
If you also read C#, use your version control client’s diff to compare the saved file with the checkpoint. Review every changed method in the file.
Review questions
Section titled “Review questions”Keep these questions beside the canvas:
- What does it call? Name every call node on each white route.
- What does it change? Include SET nodes and calls whose names say they change something, then look at what is wired into them.
- Where does it stop early? Start from every magenta EXIT node and follow its wire back to the yellow node that decides it.
A fourth question helps with a branch inside a branch: which nodes run only when both answers are yes? In the sample’s StompEnemy, the HUD refresh needs both _scoreCounter and _hud.
When it goes wrong
Section titled “When it goes wrong”When it goes wrong
| Symptom | Check | Fix |
|---|---|---|
| Changes says change review is unavailable. | Read the provider diagnostic in Changes or its tooltip. | Check the repository in your version control client. You can still open the changed class with the class picker and review its current canvas. |
| There is no Revert Method, Stage or Diff action. | Round Trip does not restore, stage or diff saved source; Changes only lists the modified classes. | Review the file diff and restore the intended changes with your version control client or backup, then let Unity import the script. |
| The canvas still shows the older method. | Look for a Unity compile or import still in progress. | Use Reload on the open method once Unity is ready. |
- Work as a team: agree who presses Compile and who reviews.
- Changes and history: understand the status actions on each method.
- Branch: follow nested true and false routes.




