Treehouse gives each Git worktree a stable ID for isolated dev setups

Treehouse, an open‑source CLI, assigns a stable numeric identifier to each Git worktree, enabling per‑worktree configuration such as ports, database names, and other service settings. The identifier persists across checkouts, so scripts can reference it without manual bookkeeping [GitHub].

The project was announced on June 6, 2026, with a README that shows a single‑command workflow: treehouse id prints the worktree’s number, which can be interpolated into environment variables or .env files. The tool reads the .git/worktrees directory to map the current directory to its worktree entry, then emits a zero‑based index that never changes for that worktree [Lobsters].

What shipped

Treehouse ships as a small binary with pre‑built releases for Linux, macOS, and Windows. Installation is a one‑liner via cargo install treehouse or by downloading a release asset. Once installed, developers add a line like export PORT=3000${TREEHOUSE_ID} to their shell profile, guaranteeing unique ports for each worktree.

Why it matters

Tying configuration to a worktree ID removes the need for ad‑hoc scripts or manual port juggling when developers run several services side‑by‑side. The deterministic IDs also let teams share a common convention, reducing merge conflicts over .env files and speeding up onboarding for new contributors.

Poll: What is your preferred method for managing multiple dev environments?

• Git worktrees with Treehouse
• Docker containers
• Virtual machines