GitHub Repository

git worktrees that actually work (zero-config dep sync, fleet mode for parallel agents)

62 starsRust

workz – one command to make any Git worktree a full dev environment

Name: workz – one command to make any Git worktree a full dev environment
Availability: InStock
Author: rohansx

by rohansx·Mar 5, 2026·2 points·1 comment

Visit Project View on HN

AI Analysis

●●SolidSolve My ProblemSlickShip It

Automates worktree setup that everyone reinvents; but worktree adoption is still niche.

Strengths

•Smart symlink strategy (node_modules, target, .venv) saves GB per worktree and actually works
•Detects 7+ package managers and auto-installs—handles Node/Rust/Python/Go/Java out-of-box
•Integrates cleanly with AI agents (Claude, Cursor, Aider, Windsurf) as setup hook, filling real gap

Weaknesses

•Audience narrow: solves pain only for developers already committed to worktree workflows
•No evidence of tested real-world multi-agent orchestration—docs show examples but no deployment stories

Post Description

Git worktrees are everywhere now — Claude Code, Conductor, Claude Squad, and most AI agent tools use them for parallel isolated sessions. But worktrees only isolate code. Your .env files, node_modules, Docker state, and ports are all missing or shared. I kept writing the same setup bash for every project, so I built workz — a Rust CLI that handles it automatically:

Auto-detects project type (Node/Rust/Python/Go/Java) Symlinks node_modules, target/, .venv, and 19 more dirs (saves GBs per worktree) Copies .env, .envrc, .npmrc, secrets (17 patterns) Auto-installs deps from lockfiles (pnpm/yarn/npm/bun/uv/poetry/pip/cargo) New: --isolated flag assigns unique ports, namespaces Docker compose, generates per-worktree DB names

Zero config. Single Rust binary. Works standalone or as a setup hook for Conductor/Claude Squad/any orchestrator.

https://github.com/rohansx/workz