Git Worktrees
CrispyVibe groups projects within a VibeSpace that are worktrees of the same repository under one repository in the Workspace side panel. From there, you can open, create, close, and delete worktrees.
Getting started
- Open the Workspace rail item (the grid icon in the side menu). Workspace is the default rail item.
- A repository with more than one worktree appears as a collapsible repository row, for example,
myrepo · 2 worktrees. - Expand it to see each worktree, labeled by branch, each with its own Files, Changes, and Chats.
Open a worktree that isn’t added
Expand the repository, open Other worktrees (N), and click Open. You can also right-click the worktree and choose Open as Project. The worktree moves into the repository group.
Create a new worktree
Click the + on the repository row and choose New Worktree…, then enter a branch name. CrispyVibe creates a sibling worktree on that branch and opens it.
Close a worktree
Right-click a worktree and choose Close Worktree. It’s removed from the sidebar but stays on disk, reappearing under Other worktrees.
Delete a worktree
Right-click a worktree, choose Delete Worktree…, and confirm. This removes the directory from disk and unregisters it from git.
If the worktree has uncommitted changes, git refuses the delete. You can then choose Force Delete, which discards those changes. The repository’s main worktree can’t be deleted.
Subdirectories stay standalone
Only folders opened at a worktree’s root are grouped as worktrees. A subdirectory you opened as its own project stays a standalone node, even when it is inside the same repository. CrispyVibe keeps it outside the repository group.
Troubleshooting
| Issue | Resolution |
|---|---|
| A worktree isn’t showing | It must belong to a git repo you’ve added. Non-git folders and SSH/remote projects aren’t grouped. |
| Delete failed | The worktree likely has uncommitted changes or is locked. Use Force Delete only if you accept losing those changes. |
| ”Other worktrees” is empty | The repo has only the worktrees you’ve already added. |
| A folder inside a repo shows as its own project | This is expected. Only folders opened at a worktree root are grouped. A subdirectory opened as its own project stays standalone. |
Known limitations
- Worktree grouping supports local repositories only; SSH and remote worktrees are unavailable.
- Branch-name validation is minimal; use normal git branch names.
- Agent-CLI commands for worktrees are unavailable.