Per-worktree environment isolation (services, databases, submodules), not just worktree lifecycle
Developers running multiple branches and AI agents in parallel via git worktrees keep hitting the same wall: worktrees isolate files but not the surrounding environment. Each worktree still shares one Docker stack and database, and `git worktree` famously won't initialize submodules, which breaks monorepos. The 2026 crop of worktree managers automates create/switch/merge but punts on per-worktree services and submodules.
The wedge the AI-agent rush exposed but nobody fixed is that parallel work needs isolated services, not just isolated files... ship Compose templating (unique ports plus namespaced volumes/DB) and conditional submodule init on `worktree add`, and stay vendor-neutral instead of bolting onto one agent CLI.
landscape (3 existing solutions)
Worktree lifecycle management is now crowded and effectively solved. The unsolved part is environment isolation: standing up isolated services/DBs per worktree and auto-initializing submodules, which every parallel-worktree tool currently leaves to the user.