We've all been there: you give an AI agent access to your files, walk away for a minute, and come back to find half your project folder deleted.
AI agents are powerful, but they're also unpredictable. They interpret instructions literally, make assumptions about what's "safe" to delete, and don't have the context to know what's important to you.
The solution? Don't let them roam free. Give them their own drive letter.
The Simple Fix
Here's what I do now:
- Create a dedicated folder for the AI agent's work
- Map that folder to a drive letter on Windows
- Point the agent only at that drive
The agent sees only that drive. It can't touch anything outside. OS-level isolation, no VM overhead.
Two Tools, Two Scenarios
I use two tools depending on where the files live:
Local Files: ScsSubst
If the agent works with local files, I use ScsSubst to map the local folder to a drive letter.
It's lightweight, portable, and one-time purchase. Way cheaper than dealing with accidentally deleted files.
Cloud / WebDAV Files: ScsDrive
If the data lives in the cloud (WebDAV, NAS, etc.), I use ScsDrive to mount the cloud folder as a drive.
Same isolation, no local safety concerns. The agent works with cloud files but still can't escape the drive.
Why This Works Better Than VMs
I tried VMs first. They work, but:
- They're slow to start
- They use a lot of resources
- Sharing files between host and VM is annoying
Drive letter isolation is instant and lightweight. The agent works with regular files on a regular drive, no special configuration needed.
Give It a Try
Next time you run an AI agent, don't give it your whole filesystem. Create a dedicated folder, map it to a drive, and let the agent work inside that drive only.
Both are one-time purchases. After losing a whole project folder, I'd say that's a bargain.
Top comments (0)