If you're using AI coding tools like Cursor, Claude Code, Cline, or Aider, you need a dedicated work drive.
Here's why.
The problem
When you point an AI agent at your real project folder, it has access to everything:
- Your
.envfile with API keys - Your production config
- Your database credentials
- Your 48,000 files
And sometimes, the agent will make a mistake. It'll delete something it shouldn't. It'll overwrite a config. It'll run a "cleanup" script that goes too far.
The solution
Give the AI agent its own drive letter.
Create a folder for the task, map it to a drive on Windows, point the agent at that drive. Now the agent's entire working universe is that drive. It can do whatever it wants inside it. It literally can't see anything outside of it.
Why this works
Because it's an OS-level boundary. The filesystem enforces it, not the AI.
The agent doesn't know it's on a mapped drive. It just reads and writes files like normal. But the filesystem makes sure it can only touch files inside that drive.
The tool I use
ScsSubst (https://subst.scsoi.com/) — $9.99 lifetime, one-time purchase. It makes persistent drive mappings that survive reboots, and gives you a GUI to manage all your drives.
The workflow
- Create a folder for the task
- Map it to a drive
- Point the AI agent at it
- Do the work
- Review the results
That's it. Five steps. Takes 10 seconds.
The bottom line
AI coding tools are powerful. But they're also unpredictable.
Give them their own drive. And you'll never have to worry about them deleting your files again.
Top comments (0)