Checking edits
See exactly what Panda changed in your files, open any file it touched, and put back what you do not want before you commit.
How-to guide Updated 20 Nov 2026What you get
Every file Panda changes shows up in the chat as it happens, and the Review panel collects them all in one place. You read the changes there, put back what you do not want, and only then commit.
Check what changed
- Read the edit rows in the chat.
Each edit names the file and how many lines were added and removed, for example +12 -3. A new file says new. Click the row to see the change: removed text in red, added text in green. - Open a file Panda touched.
Click the file name in the row. The file opens beside the chat. - Press Review at the top of the chat.
The Review panel lists every changed file with its added and removed lines. Pick Last turn to see only what Panda's last answer changed, or Git changes for everything not committed yet. Click a file to read its changes, side by side with Split or in one column with Unified. - Comment on a line.
Click its line number, Shift-click to stretch to more lines, write what to change and press Add comment. Send to this chat sends every comment as one review. Tick Viewed on a file you have read. The tick clears when the file changes again. - Put back what you do not want.
Hover the file and press Revert changes. In Last turn the file goes back to how it was before that turn. In Git changes it goes back to the last commit. PandaOS asks first, because this cannot be undone. - Commit what you keep.
Open the Git panel, check the files under Staged Changes, write a message or press Generate for one, then press Commit.
Undo everything since a message
Hover one of your own messages and press Rewind. PandaOS first tells you how many files it would put back, and View changes shows them in the Review panel before you decide. Rewind sets those files back to how they were when you sent that message. In OpenCode chats the same button asks to revert the conversation to that message instead, without a file count. Codex chats do not offer it.
Approve each edit before it happens
To see every change before it is made, pick Ask first in the mode menu of the message box. Panda then asks before every file change and every command. Auto-edit lets file edits through and still asks before commands. When Panda asks, you answer Allow, Deny or Always allow. The third button reads Allow for session when the answer lasts for this chat only. Details shows the text it wants to replace and what replaces it. See Permissions.
If it does not work
- Rewind says it can't rewind to this message. No file changes were kept for it. A forked chat starts without the original chat's saved points, and saved points expire after 30 days. Use Git changes in the Review panel and revert the files there.
- Revert says the file is not in the turn snapshot. Panda created that file during the turn, so there is no earlier version to go back to. Delete the file instead.
- Review says No uncommitted changes. Everything is committed already. Pick Last turn to see what Panda's last answer changed.