Create and remove worktrees
Create a worktree per branch, and see what you would lose before removing one.
Creating
Section titled “Creating”Start from the Worktrees tab in Git mode.
- By repo view: click + (Add worktree) next to a repository name.
- By status view: click Add worktree below the list. With several repositories, pick one first.
Fill in the New worktree dialog.
- Task type: Feature, Bug fix, Refactor or Change. Shown only when the repository uses work plans (see Work plans). requirements.md is pre-filled from the template of that type.
- Branch name: the new branch. It starts from the repository’s current HEAD.
- Folder: where the worktree goes.
Default folder
Section titled “Default folder”- If the worktree hook is on in the Agents tab of the settings,
~/.belloga/worktrees/{owner}/{repo}/{branch}is filled in. Claude Code in a Belloga terminal is also told to use this location before it creates a worktree. - Otherwise, a folder next to the repository is filled in, named after the branch with
/replaced by-.
Either way, you can edit it in the dialog.
Removing
Section titled “Removing”Pick Remove worktree from the More actions menu on a worktree card. The repository’s main worktree can’t be removed.
Before removing, the dialog counts what you would lose.
- Commits not pushed, or a branch with no copy on the remote
- Changed files
- Stashes left in the repository
- Tabs that close with it and unsaved documents
If there is nothing to lose it says “Nothing will be lost.” Removing first ends the terminals running in that folder, then deletes the folder. The branch stays.
Open in VS Code
Section titled “Open in VS Code”Pick Open in VS Code from the card’s More actions menu to open the worktree folder in VS Code.