Recursive deletes wait for an owner
Recursive deletes, cleans and drops are blocked until someone allows them.
A delete, stopped
- Nothing to restore
- The delete never runs, so nobody has to recover the files.
- Allowed once, on purpose
- The agent or person asks from the record. An admin allows it once or for a while, and the retry passes.
- One command, not a blanket pass
- An exception covers the command it was granted for, once or for a while, and the record keeps it.
The Destructive operations policy
Recursive deletes, drops and cleans outside the working tree.
- It installs as Observe, so you see your own traffic first. Turn it to Block when you are ready.
- The adapter cannot tell the working tree from the rest of the disk for a command, so recursive deletes anywhere are watched.
- Drops inside a database session (DROP TABLE in psql) are not visible as commands.
Related use cases and clients
- Protected branchesForce pushes and history rewrites are blocked before they run, until someone allows one.
- Secrets and env filesFile reads and writes of env files, keys and credentials are blocked, and sending them is flagged by the read scan.
- Set up Claude CodeEvery shell command, edit, read, fetch and MCP call in Claude Code passes the adapter before it runs.