Here's the workflow I've been using for the past few months that has completely changed how I work with AI coding agents.
Step 1: Create a new drive for each task
Every time I start a new AI task, I create a new folder and map it to a drive letter. I use ScsSubst (https://subst.scsoi.com/) for this — it's a $9.99 lifetime tool that makes persistent drive mappings on Windows.
C:i-workspaces ask-001\ → Z:
C:i-workspaces ask-002\ → Y:
C:i-workspaces ask-003\ → X:
Step 2: Point the AI agent at the drive
I open Cursor / Claude Code / whatever tool I'm using, and point it at Z:\ instead of my actual project folder.
The agent works entirely inside that drive. It can read, write, delete, refactor — whatever it wants. It's a sandbox.
Step 3: Walk away
No approval gates. No "are you sure?" prompts. No hovering over the keyboard.
I go do something else. The agent works.
Step 4: Review the results
When I come back, I review everything inside the drive. If it's good, I copy the result to my real project. If it's garbage, I delete the drive and start over.
Why this saves me 10 hours a week
Before this workflow:
- I spent hours babysitting the agent
- I had to carefully curate every prompt
- I was scared to leave it running for more than 10 minutes
- I spent half my time cleaning up after mistakes
After this workflow:
- I spend 10 minutes setting up the drive
- I let the agent run for hours
- I review the results when I'm done
- No cleanup needed — just delete the drive
The bottom line
Giving the AI agent its own drive letter didn't just make it safer. It made it faster. Because I stopped micromanaging and started letting it work.
That's the real ROI.
Top comments (0)