Reviewing & Restoring Changes · Docs

All modifications the agent makes are recorded as a ChangeSet. Review them line by line or undo them wholesale — every delivered step is recoverable.

Reviewing changes

In a task's change view you can:

Task-level summary: which files changed, how many lines added or removed;
Per-file diffs: an editor-grade diff view, precise to the line;
Each file links back to the tool call that changed it — you can trace who changed what and when.

Restoring changes

VibeSpace restores in two phases:

Preflight: the app checks the restore against current file state (files you edited by hand are flagged) and lists exactly what will be rolled back;
Confirm: after confirmation, files return to their pre-task state.

Note: restores are per task. If you edited files after the task finished, read the preflight report carefully so your own edits are not overwritten.

Relationship with Git

VibeSpace never runs git commit / push and does not require the workspace to be a Git repository;
If the workspace uses Git, the ChangeSet does not interfere with your staging area — when and how to commit is entirely up to you;
Recommended flow: let the agent finish → review the ChangeSet → run git commit yourself.

A typical loop

Start task → agent edits files → review diff
  ├─ happy → keep, commit yourself
  └─ not happy → preflight restore → refine the prompt and rerun

After a restore, simply start a new task — previously approved operations do not need to be authorized again.