If you're running AI agents on your Windows machine, you need to read this.
AI agents are amazing for productivity — they can write code, organize files, automate workflows. But they also have a dangerous habit: they delete things they think are "unnecessary".
I learned this the hard way. An AI agent once deleted my entire project folder because it thought the files were "temporary". I spent hours recovering from backups.
The Solution: Give the Agent Its Own Drive
The simplest and most effective solution is to give the AI agent its own drive letter.
Here's how:
- 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 for 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 Beats Every Other Approach
I've tried:
- VMs — slow, heavy, annoying to share files
- Containers — requires Docker setup, still complex
- Restricted user accounts — clunky, doesn't fully isolate
Drive letter isolation is:
- Instant — map a folder and you're done
- Lightweight — no VM overhead
- Simple — the agent sees a regular drive, no special config
- Cheap — way cheaper than backup software
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)