01 / BranchHarbor
One feature, many repositories
Select the repositories a feature needs and create a separate Git worktree for each. Your original checkout branches and uncommitted files stay in place.
FGit worktrees / Multi-root workspaces
BranchHarbor.
One feature, many repositories. BranchHarbor by Ameyon Labs brings them into one saved VS Code multi-root workspace. Work on parallel features without repeatedly switching your original checkouts.
01The workflow
Keep related work together.
A frontend, a service, and a shared library can belong to one feature without sharing one repository. BranchHarbor creates a worktree in each selected repository and groups those folders in one saved workspace.
Add existing repositories, name the feature, choose its repositories and branch, then review the creation plan. Reopen saved features from the BranchHarbor section of Explorer.
Worktrees share Git history and objects with their source repository. They are separate working directories, not independent backups or security sandboxes.
Setup and support02In the current preview
Less switching. More context.
02 / BranchHarbor
A reusable repository catalog
Register existing Git checkouts once. Mark repositories Common to preselect them, or Optional to include them only when needed.
03 / BranchHarbor
Parallel workspace windows
Save each feature as a multi-root .code-workspace file and reopen it in a new VS Code window. Keep several features open side by side.
04 / BranchHarbor
An explicit starting point
Choose the branch name and starting revision for new branches. Existing local branches are reused at their current tip when not checked out elsewhere. No fetch runs.
05 / BranchHarbor
Checks before removal
Removal checks for changed, untracked, and ignored files, hidden index flags, and detached HEADs. Branches, commits, saved workspace files, and extra feature-folder files are kept.
06 / BranchHarbor
Data on your workspace host
No extension account, analytics, or telemetry. The catalog and generated files stay on your machine or selected remote extension host. Configured Git content filters may use the network.
Describes version 0.1.0, reviewed November 11, 2026. Preview behavior and availability may change.
03Requirements and boundaries
Your repositories. Your environment.
Use desktop VS Code 1.95 or newer with Git available on PATH, existing repositories with at least one commit, and a trusted workspace. Remote SSH and development containers use repositories and storage on that remote host. Browser-only VS Code and virtual filesystems are not supported.
The extension does not clone, fetch, pull, push, reset, stash, delete branches, or install dependencies. It does not initialize submodules or set up Git LFS. Repository content filters already configured in Git may run programs or contact services during checkout.
Generated workspaces set a window title. Existing workspace-level settings, tasks, launch configurations, secrets, ignored files, dependency folders, and uncommitted changes are not copied. Tracked repository files, including .vscode files, remain part of the checkout.
Back up important work. Before removal, preserve local files, close other windows using the feature, and stop background writers. Checks cannot protect unsaved buffers in another window or make filesystem changes by unrelated processes atomic.
04Availability
Preview release.
Version 0.1.0 is available as an initial preview on the Visual Studio Marketplace. Install BranchHarbor from the Ameyon Labs Inc. publisher.
BranchHarbor is licensed for personal or business software development under the license included with the extension. It is not offered under an open-source license.
Install from MarketplaceBranchHarbor / Information