The 6-Terminal Pipeline

A PowerShell script launches 6 cmd windows in a 3x2 grid across my monitors. Each one runs Claude Code with --dangerously-skip-permissions. Each terminal gets a non-overlapping set of files to work on.

The pipeline coordinator — me, in a 7th window on the Claude desktop app — assigns tasks, tracks file locks, and reconciles documentation when the parallel sessions inevitably step on each other's docs. Sometimes I have one or two more sprinkled in for miscellaneous tasks. The whole world turns off when I'm in it. All that exists is the terminals.

At peak velocity: 5.9 million tokens consumed in a single day. 415 sessions. I got the Pro Max subscription on Monday. By Thursday I'd burned through 75% of the biweekly allocation.

The file locking system is just a folder of .lock files. Simple. Effective. Occasionally ignored by overeager terminals.

After 6-way parallel execution, I spent an hour reconciling 35 missing PATCH_HISTORY entries. 8 passes are permanently unrecoverable — we'll never know what they did.

This isn't how games are supposed to be made. But it works.