AI agents are powerful tools. But with great power comes great responsibility - especially on your filesystem.
The problem
You give an AI agent access to your computer. It starts reading files, modifying code, running commands. Then one day it deletes something important.
The simple solution
Give the agent its own drive letter.
How it works
- Create a workspace folder for the AI
- Map it to a drive letter (like Z:)
- Point the agent at Z:4. It can only see and touch what's on Z:
Why this works
- Drive letters are OS-level boundaries
- Every program respects them
- No Docker container overhead
- Takes 30 seconds to set up
Tools
- Local folders: subst.scsoi.com
- WebDAV/cloud: drive.scsoi.com
Both are one-time purchases.
Start today
Don't wait for the accident. Set up the drive letter first.
Top comments (1)
drive letters are a good lightweight way to do spatial isolation without the docker overhead.
but spatial isolation doesn't fix behavioral loops. if the agent gets stuck in a retry loop writing files, it will just fill Z: with garbage until the disk hits 100%.
do you have a watchdog or execution timeout to kill the process if it writes 100 files in 10 seconds?