F.3BranchHarbor / Support

A clear path from setup to cleanup.

Setup, troubleshooting, and support for the BranchHarbor preview.

VS Code 1.95+ / Git on PATH / Trusted existing repositories

01Getting started

Your first feature workspace.

Check the product page for current installation availability. Once installed, open the Command Palette and use these commands:

BranchHarbor: Add Repository. Select existing Git checkouts and mark them Common or Optional.
BranchHarbor: Choose Worktree Storage Folder. Optionally select a folder outside your source repositories. The default is the extension’s global storage; a change applies only to new features.
BranchHarbor: Create Feature. Enter a name, select repositories, choose the branch and starting revision, then review and confirm the plan.
Open in new window. Use the prompt after creation or the BranchHarbor section of Explorer. Repeat to keep several features open.
BranchHarbor: Remove Feature Worktrees. When finished, preserve files, close other feature windows, stop writers, and review the removal prompt.

02Troubleshooting

Checks before you retry.

Git or a repository is unavailable

Install Git and make it available on PATH. Select an existing non-bare repository with at least one commit and trust the workspace. In Remote SSH or a development container, Git and repository paths must be available on that host.

A branch is occupied or a base is missing

Choose a branch not checked out in another worktree, or finish that other work first. The starting revision must resolve in every selected repository. Fetch missing remote references yourself if needed; the extension never fetches automatically.

Creation was interrupted

Completed worktrees and branches are preserved, and the feature can appear with an error status. Open the feature to inspect completed members, or remove its clean worktrees and create a fresh feature. No automatic rollback is performed.

Removal is blocked

Preserve changed, untracked, and ignored files, including dependency folders and .env files. Clear assume-unchanged or skip-worktree flags only after preserving their contents. A detached HEAD needs a retaining local branch. Close other windows and stop background writers before retrying. Branches, commits, workspace files, and extra feature-folder files are kept.

An operation lock remains after VS Code exits

First close every VS Code window using the extension and ensure the operation has stopped. Remove only the operation.lock file at the exact path shown in the error, then reopen VS Code. Never remove catalog.json or worktree folders to clear a lock.

Workspace settings or dependencies are missing

Generated workspaces set only the window title. Workspace-level settings, tasks, launch configurations, secrets, ignored files, dependencies, and uncommitted changes are not copied. Configure the new workspace and install dependencies manually. Tracked repository .vscode files remain part of the checkout.

03Contact

Tell us what happened.

Email [email protected] for help, bug reports, feature requests, or a suspected security issue. Support is provided by Ameyon Labs Inc., Edmonton, Alberta, Canada.

Include the extension version, VS Code version, operating system, Git version, whether you use a remote host, the command you ran, expected and actual results, and a redacted error message. A minimal reproduction with disposable repositories is helpful.

Do not send passwords, tokens, proprietary source code, or confidential repository names and paths. Review screenshots and diagnostic text before attaching them. No automatic diagnostic upload occurs.

Email extension support

BranchHarbor / Information

Read the details.

About the extension Privacy policy Terms and license