FAQ

My files go to the Trash when I delete them. Isn't that an undo?

Not for agents. rm, rimraf, Node's fs.rm, Python's shutil.rmtree and git clean all skip the Trash and Recycle Bin. In cline#15023 the Recycle Bin was empty. undomap shows the Trash under probes but never counts it.

Why is a whole .git in Zone VE?

If a repo has no remote, its history exists only in .git. One rm -rf of the project directory takes the files and every way back to them. A git bundle is a single file you can keep anywhere.

Clean tracked files are "undoable". What if the agent deletes .git too?

Then they're only as safe as your remote. That's why "no remote" is permanent and "unpushed commits" is slow undo. Zone X assumes .git survives, which is the common case for file-level edits and deletes.

Time Machine is on. Why is something still in Zone VE?

undomap asks tmutil isexcluded for each fragile path. Big folders (datasets, VM images, ~/code itself) are often excluded on purpose. They show as VE with no snapshot.

My project is in Dropbox / OneDrive / Google Drive / iCloud. Isn't that a backup?

Partly. The client copies the agent's delete to the cloud within seconds, so the undo is the provider's version history (30 days on most plans). undomap detects the folder and counts that history only when it can verify it: the client's own config points there, the client is running, and the path isn't one the provider skips (Dropbox-ignored folders, .nosync, temp files, files over the size limit). iCloud Drive brings back deleted files but not overwritten ones, so it never counts. Everything else stays Zone VE, marked possible cloud versioning, unverified, with the check to run. The full rules. If you know better, list the folder under backedUp.

It says my dist/ is regenerable, but it isn't.

Built-in names are a guess. List it under permanent in .undomap.json and it's graded Zone VE with a fix, even if it sits inside a regenerable folder ("permanent": [".cache/models/"] carves just that subfolder out). If it's protected some other way, use backedUp instead. See precedence.

Does it read file contents?

Only the first 4 bytes of gitignored or untracked files, to spot compiled binaries. Everything else is lstat and git metadata. Nothing leaves your machine. The landing page draws dropped JSON in the browser tab.

Does --reach read my secrets?

No. It looks for credentials the way ls would: names, paths and permissions. Credential files are never opened, environment variables are judged by name, and only the name is printed. Finding what's inside files or transcripts is spillscan's job.

How is this different from agentckpt, blast-radius tools or command blockers?

Blockers stop commands. Checkpoint tools (like agentckpt) save state. Post-mortem tools read transcripts after the fact. undomap is the pre-flight audit: where would a mistake cost you something you can't get back?

Back to Overview