worktree

Managing Git worktrees for parallel feature development is done by creating isolated workspaces with separate dependency installs and port assignments. This allows multiple feature branches to be developed side-by-side without polluting the main environment.

Isolating dependencies and ports across multiple Git branches is achieved by generating per-worktree .worktree.json configurations. Each worktree gets its own isolated dependency installation and coordinated port assignment to prevent conflicts.

Creating, listing, and closing Git worktrees is automated through a Makefile-driven workflow that avoids direct calls to cargo, npm, or npx. You use the worktree command to manage the lifecycle and start development via Makefile targets.

Closing a worktree does not require manual process stopping or branch pruning. The closing and cleanup process automatically stops dev processes and prunes branches when you are done with the feature.

Building MCP servers and installing dependencies within an isolated worktree setup is supported. The automation parses arguments, generates configurations, installs dependencies, builds MCP servers, and guides users from setup to launch.

Using a Makefile for consistent builds in worktrees prevents environment drift by enforcing a unified workflow. All commands are driven through the main Makefile to ensure consistent builds and avoid direct calls to cargo, npm, or npx.