History and saved versions
Use History to review pending AI edits, inspect activity, search saved versions and restore an earlier accessible project state safely.
Guides follow the current project source. Check the release notes for your installed version.
Select the project first
The activity and saved-version timeline follows the selected approved project. Choose the intended project in the Projects rail, then inspect its recorded work and local file versions.
Pending AI Review changes can span approved projects. Check each request’s workspace name and paths before applying or rejecting it. The Checkpoints manager can also switch between Active project only and All projects; a pending request has not changed the project yet.
Review a pending request
In AI Review, inspect the request’s workspace label, paths and prepared diff before choosing the local approval or rejection control. RepoTunnel revalidates the live file before applying a prepared text change; another editor’s intervening changes can make that request stale.
AI Auto applies compatible changes immediately and records their outcome. Read-only access still blocks writes, and an AI cannot approve its own pending request through MCP.
Find the activity you need
Search history by the visible record text, select an activity filter and choose newest or oldest first. Load More reveals additional records when the first page is insufficient.
The filters include Files, Terminal, Processes, Apps, Browser, Git, Verification, Monitoring and Team. Expand a record to inspect its recorded outcome instead of treating a request or started process as a completed task.
Understand versions and request grouping
File-changing requests can have a local restore point. When a client supplies a usable request trace, RepoTunnel can group the related mutations into one version. Without that trace, changes remain protected but can be stored as separate versions.
Terminal, browser and other activity can appear alongside the file version. Restoring files does not promise to reverse every external side effect recorded in that activity.
Return to a saved file state
Select Restore this version on the intended saved entry and review the local confirmation. Previous and Next navigate saved version state; Restore original targets the state captured before the first AI edit.
Later saved versions remain available after a version restore, so you can return to them. Check the returned result, inspect the project and run the appropriate verification before resuming edits.
Undo and restore have different scope
Undo reverses a supported individual change only while the relevant current contents and paths still allow safe recovery. Version restore targets a saved project-file state.
Some destructive operations remain auditable without automatic Undo, including recursive removal or deletion that could not be backed up safely as bounded text. Inspect the specific record’s available recovery controls.
Manage retention deliberately
Clear All History removes saved versions and activity for that project after local confirmation. Current project files stay as they are, and pending AI Review requests remain available.
Use Settings for the configured version-history and checkpoint retention limits. Clearing saved recovery data removes recovery options; it is a separate decision from accepting an edit.