Skip to main content
Git worktrees provide isolated workspace environments for different branches, allowing you to work on multiple features simultaneously without switching between branches. When enabled, VibeKit automatically creates separate worktrees for each branch operation.

Configuration

Enable worktrees in your VibeKit setup:

How It Works

When worktrees are enabled:
  1. Branch Creation: Each new branch gets its own isolated directory
  2. Automatic Setup: VibeKit automatically creates worktrees based on branch names
  3. Isolation: Changes in one worktree don’t affect others
  4. Cleanup: Worktrees are automatically removed after operations (unless cleanup: false)

Usage Examples

Generate Code in Feature Branch

Execute Commands in Worktree

Create Pull Request from Worktree

Benefits

Parallel Development

Work on multiple features without branch switching

Clean Isolation

Each branch has its own workspace and dependencies

Automatic Management

No manual worktree commands needed

Safe Operations

Changes are isolated until merged

Configuration Options

Advanced Usage

Custom Worktree Root

Disable Cleanup

Multiple Branches Example

Worktrees are particularly useful in CI/CD environments and when working with large codebases where branch switching is expensive.
Ensure your git repository has a clean state before enabling worktrees. Uncommitted changes may cause issues during worktree creation.