Using Virillio Code
Reviewing and undoing
Inspect the actual changes, request corrections, and recover carefully.
On this page
Review a completed change
Before keeping a result, inspect the files the agent changed. Open the review or diff view available in the session and compare additions and removals with your original request.
Check both intended behavior and nearby behavior. Read test output for failures, skipped tests, or missing dependencies. If a check could not run, treat it as unverified.
Give targeted feedback
Use a filename and a concrete observation when asking for a correction:
In the settings form, keep the Save button disabled until something changes.
The current implementation enables it immediately. Fix that and verify both states.Review the updated diff after the correction. An explanation that sounds right may still hide an unrelated file change.
Undo with care
The session’s Undo action can return to an earlier point in the work; Redo is available where the session supports it. Inspect the affected files after either action.
Keep a Git commit or backup before larger changes. Undo in a coding session cannot reverse everything a command or connected service might do: remote deployments, sent messages, database changes, and other external effects need their own recovery process.
Finish the task
Run the project’s relevant checks and exercise the changed feature. Commit or publish once the result is correct and you have intentionally authorized that final action.