Worktrees on autopilot
Assign a worktree per task manually, or flip one setting and every new task gets one automatically. Isolated branches, isolated directories. Merge conflicts between tasks become structurally impossible.
Worktrees are how SlayZone turns parallel task execution from a discipline problem into a default. Each task can get its own branch and working directory without manual setup friction.
That isolation means tasks stop stepping on each other at the filesystem layer. You can keep several refactors, fixes, and experiments moving at once without constant stashing and switching.
The app treats worktree lifecycle as part of task lifecycle so the overhead stays low enough to use on every task, not just the big ones.
Have a question about how this works in practice? Check the SlayZone FAQ or read about all features.