workz fixes that automatically. It symlinks heavy directories (node_modules, target, .venv) and copies .env files into every new worktree. Zero config — it detects your project type from lockfiles.
But the thing I'm most excited about is fleet mode, added in v0.5:
workz fleet start \
--task "add user authentication" \
--task "refactor the database layer" \
--task "write integration tests" \
--agent claude
That creates 3 isolated worktrees, syncs deps into each, writes a .workz-task.md
with the task description, and launches Claude in all three simultaneously. Each
agent works on its own branch with no interference.v0.6 adds `workz serve` — a local web dashboard at localhost:7777 showing all your worktrees as cards with status, last commit, actions (sync, open in VS Code/Cursor, remove). Fleet worktrees get their own section showing the task.
v0.4 added an MCP server so Claude Code can manage worktrees autonomously: claude mcp add workz -- workz mcp
Stack: Rust, single binary, ~5MB. Ships for macOS and Linux.
cargo install workz
brew install rohansx/tap/workz
GitHub: https://github.com/rohansx/workzHappy to answer questions about the architecture — the worktree + symlink strategy and the MCP integration were the interesting design problems.