DEV Community

疏影
疏影

Posted on

Why I Stopped Letting Claude Code Touch My Main Drive

After Claude Code deleted half my node_modules folder during a refactor, I changed my setup. Now every agent session gets its own drive letter on Windows.

What I used to do

Just let Claude Code run in whatever project folder. It could read everything, write everywhere, and one bad rm -rf command could take down half my machine.

The fix

Map the agent workspace to its own drive letter. The agent sees only that drive, can only write to that drive. If it goes rogue, it trashes its own sandbox - not your photos, not your other projects, not your production config.

  • Local folder sandbox: subst.scsoi.com maps any local folder to a real drive letter
  • WebDAV/cloud sandbox: drive.scsoi.com mounts WebDAV/storage as a drive letter

Both are one-time purchases, no subscription. OS-level isolation, lighter than Docker, no VM overhead.

Why this beats Docker

Docker works but it's heavy for a coding agent. Drive letter mapping is instant - the agent sees a normal drive, can use any tool, no path translation, no container networking mess.

Give it a try before your next rm -rf incident.

Top comments (0)