Start here
The free tool below runs entirely in this browser — no account, nothing stored or transmitted. Redact anything you would not want kept before you type it.
Open the companion tool →Why the agent log and the file service history are different records
An agent, sync client, or shared editor may create, replace, rename, move, or delete a file. The file's version history can differ from the agent's activity log, and workspace permissions may hide or disable versioning.
Microsoft and Google document version and activity controls for supported cloud files, but retention, permissions, and restore behavior differ by product and account. Do not assume a restore also recovers every comment, sharing permission, or collaborator's latest change.
The protocol
- Pause the agent's write actions using its own controls. Do not empty a recycle bin or repeatedly overwrite the current file; for work data, notify the owner or administrator.
- Identify the file by a non-sensitive name or alias, storage location, owner, change time, agent or app involved, and the operation you observed.
- If permitted by your workplace and service rules, preserve a copy of the current state and record the version or activity entries before trying a restore.
- Open the storage provider's version history directly and compare the available versions, timestamps, and ownership; some file types have different history controls.
- Restore only a version you have checked, then verify the result with the owner. Review and narrow the agent's file permissions before resuming automation.
What the tool does
Build an AI-agent file-change recovery record. It runs locally in this browser and sends nothing.
Limit first: This is a recovery-planning aid, not technical, legal, or workplace advice. It cannot restore a file, prove which system caused a change, or guarantee that an older version exists.
Open the companion tool →Cost and free path
Cost: Free: one complete local run in this browser, with no account or upload; the tool does not transmit what you enter. Optional $4 one-time convenience unlock for unlimited runs of this tool on this browser; never a subscription. The protective answer and every free-path step remain free.
Automated decision this documents: an autonomous AI agent or AI-assisted editor with permission to create, overwrite, move, or delete files in a cloud workspace
Free path, in order (no cost):
- The cloud provider's built-in version and activity history for the affected file
- The file owner or workspace administrator, especially for shared or work-owned data
- The agent provider's official support and permission-revocation controls
What this cannot do: It cannot restore a file, prove which system caused a change, or guarantee that an older version exists.
Sources checked 2026-10-10 · first-party source pages fetched and reviewed; no separate raw HTTP-status probe.
One human next step
Open the storage service directly and check its own version history before restoring. If the file is shared or work-owned, ask the owner or administrator to confirm the correct version and access changes; then restrict the agent's write access until the incident is understood.
Research log and safety checks
AI-assist path: no model inference is used to authenticate external material, restore a file, change a record, or decide a rights dispute. The tool structures user-supplied facts and points to independent source channels; a model call would add no verified evidence. §0.5 protection result: the tool does not make an external decision; crisis-adjacent: no; fear/urgency/scarcity toolkit used: no.
§0.5 protection result: category is data-privacy-exposure; crisis-adjacent: no; fear/urgency/scarcity toolkit used: no. The protective function is free and the paid feature is convenience only.