Review changes and undo

Every file an agent writes shows who wrote it and what changed, in plain words with the exact lines one click away. Nothing lands in your files without an owner, and nothing is hard to take back.

The Changes tab

1. Open Changes beside the conversation. Each file shows who changed it and one plain line about what changed.
2. Expand a file to see the changes. For each one you can Keep, Reject or comment. Click a green line to comment on exactly that line.
3. A rejected change is undone on disk and the next run is told about it, so the team does not just redo it.
4. Send review comments (n) hands all your comments to the team as one follow-up message.

Ways to go back

Versions without git jargon

The Versions tab shows what changed, lets you choose what to include, save a version, switch branches, upload and download, and read the history, all in plain messages. If git is not installed or the folder is not a repository, the tab says so in plain words.

Who changed what

The Files tab can show, for each file, who last changed it, when and why, with a link back to the conversation and to the saved copy from just before. It is built from what the team and you did, not guessed. A file changed outside Maxtkn is not listed.

Checks after a run

• Your own checks. After the team edits, Maxtkn runs the project tests and build. A failure goes back to the team to fix, up to a limit you can see.
• Browser checks. An agent can open your running app in a real browser, read the page, click, type and take screenshots. Addresses on your local network are blocked.
• Acceptance checks in plain sentences. Write “the Add button adds a task” and get a stored check you can run again. Results show in a Checks tab.
• A reviewer. After a run, a reviewer lists findings you can jump to. Fix one with a click or dismiss it for good.
• Explain this. Ask for any change, error or command to be explained, at the depth you choose. It never invents details.

The final walkthrough lists the evidence that was collected. It is built from what the checks found, not from the model grading its own work. A check that could not run is reported as not run, never as a pass.

Keep a record

From the thread menu, Share → Save this thread writes a record of who did what and when. Each step is linked to the one before it, so a later change to the file can be found, and an optional seal can be added. A separate verification script can check a record without the app; it is part of the project source, not of the installer.