Stop Letting AI Agents Touch Your C: Drive

A developer published a method for sandboxing AI coding agents on Windows by mapping the agent's workspace to its own drive letter using the built-in subst command, rather than relying on Docker or a VM. The approach confines the agent to a single drive so it cannot read or modify files outside that workspace, such as the .ssh folder or hosts file. The tools are offered as one-time purchases.

Your AI coding agent can read your .ssh folder. It can edit your hosts file. It can delete your whole C: drive if it goes wrong. Why are you letting it? The fix Map the agents workspace to its own drive letter. Done. - Local folder workspaces: subst.scsoi.com - WebDAV/cloud workspaces: drive.scsoi.com The agent sees a normal drive. It writes there happily. It cannot see anything outside that drive. No containers needed You dont need Docker Desktop. You dont need a VM. You just need Windows drive mapping, which has existed for 30 years. Both tools are one-time purchases. Set it up once, run agents worry-free forever.