A CLI tool for easy Git Worktree management.

日本語

# Create a worktree with a new branch
vibe start feat/new-feature

# Use an existing branch (or re-run if worktree already exists)
vibe start feat/existing-branch

# After work is done, delete the worktree
vibe clean

vibe start handles the following situations:

• When a branch is already in use by another worktree: Confirms whether to navigate to the existing worktree
• When the same worktree already exists: Automatically re-uses it (idempotent)
• When a directory exists with a different branch: You can choose from the following options
  • Overwrite (delete and recreate)
  • Reuse (use existing directory)
  • Cancel

# Example when branch is already in use
$ vibe start feat/new-feature
Branch 'feat/new-feature' is already in use by worktree '/path/to/repo-feat-new-feature'.
Navigate to the existing worktree? (Y/n)

brew install kexi/tap/vibe

deno install -A --global jsr:@kexi/vibe

Permissions: For more security, you can specify exact permissions instead of -A:

deno install --global --allow-run --allow-read --allow-write --allow-env jsr:@kexi/vibe

Using with mise: Add to your .mise.toml:

[tools]
"jsr:@kexi/vibe" = "latest"

Then run:

mise install

Note: WSL2 users can use the Linux installation methods below based on their distribution.

# x64
curl -LO https://github.com/kexi/vibe/releases/latest/download/vibe_amd64.deb
sudo apt install ./vibe_amd64.deb

# ARM64
curl -LO https://github.com/kexi/vibe/releases/latest/download/vibe_arm64.deb
sudo apt install ./vibe_arm64.deb

# Uninstall
sudo apt remove vibe

# x64
curl -L https://github.com/kexi/vibe/releases/latest/download/vibe-linux-x64 -o vibe
chmod +x vibe
sudo mv vibe /usr/local/bin/

# ARM64
curl -L https://github.com/kexi/vibe/releases/latest/download/vibe-linux-arm64 -o vibe
chmod +x vibe
sudo mv vibe /usr/local/bin/

# Download
Invoke-WebRequest -Uri "https://github.com/kexi/vibe/releases/latest/download/vibe-windows-x64.exe" -OutFile "$env:LOCALAPPDATA\vibe.exe"

# Add to PATH (first time only)
$path = [Environment]::GetEnvironmentVariable("Path", "User")
[Environment]::SetEnvironmentVariable("Path", "$path;$env:LOCALAPPDATA", "User")

deno compile --allow-run --allow-read --allow-write --allow-env --output vibe main.ts

Add the following to your shell configuration:

vibe() { eval "$(command vibe "$@")" }

vibe() { eval "$(command vibe "$@")"; }

function vibe
    eval (command vibe $argv)
end

def --env vibe [...args] {
    ^vibe ...$args | lines | each { |line| nu -c $line }
}

function vibe { Invoke-Expression (& vibe.exe $args) }

Place a .vibe.toml file in the repository root to automatically run tasks on vibe start. This file is typically committed to git and shared with the team.

# Copy files from origin repository to worktree
[copy]
files = [".env"]

# Commands to run after worktree creation
[hooks]
pre_start = ["echo 'Preparing worktree...'"]
post_start = [
  "pnpm install",
  "pnpm db:migrate"
]
pre_clean = ["git stash"]
post_clean = ["echo 'Cleanup complete'"]

Trust registration is required on first use with vibe trust.

The files array supports glob patterns for flexible file selection:

[copy]
files = [
  "*.env",              # All .env files in root
  "**/*.json",          # All JSON files recursively
  "config/*.txt",       # All .txt files in config/
  ".env.production"     # Exact paths still work
]

Supported patterns:

• * - Matches any characters except /
• ** - Matches any characters including / (recursive)
• ? - Matches any single character
• [abc] - Matches any character in brackets

Notes:

• Directory structure is preserved when copying matched files
• Recursive patterns (**/*) may be slower in large repositories
  • Use specific patterns when possible (e.g., config/**/*.json instead of **/*.json)
  • Pattern expansion happens once during worktree creation, not on every command

Vibe automatically verifies the integrity of .vibe.toml and .vibe.local.toml files using SHA-256 hashes. This prevents unauthorized modifications to configuration files.

• When you run vibe trust, Vibe calculates and stores the SHA-256 hash of the configuration files
• When you run vibe start, Vibe verifies the file hasn't been modified by checking the hash
• If the hash doesn't match, Vibe exits with an error and asks you to run vibe trust again

You can disable hash verification in your settings file (~/.config/vibe/settings.json):

Global setting:

{
  "version": 3,
  "skipHashCheck": true,
  "permissions": { "allow": [], "deny": [] }
}

Per-file setting:

{
  "version": 3,
  "permissions": {
    "allow": [
      {
        "repoId": {
          "remoteUrl": "github.com/user/repo",
          "repoRoot": "/path/to/repo"
        },
        "relativePath": ".vibe.toml",
        "hashes": ["abc123..."],
        "skipHashCheck": true
      }
    ],
    "deny": []
  }
}

Note: Version 3 uses repository-based trust identification. Settings are automatically migrated from v2 to v3 on first load. Trust is shared across all worktrees of the same repository.

Vibe stores multiple hashes per file (up to 100), so you can switch between branches without needing to re-trust files (as long as you've trusted each branch's version at least once).

Create a .vibe.local.toml file for local-only configuration overrides that won't be committed to git (automatically gitignored). This is useful for developer-specific settings.

# Override or extend shared hooks with local commands
[hooks]
post_start_prepend = ["echo 'Local setup starting'"]
post_start_append = ["npm run dev"]

# Override files to copy
[copy]
files = [".env.local", ".secrets"]

When both .vibe.toml and .vibe.local.toml exist:

• Complete override: Use the field name directly (e.g., post_start = [...])
• Prepend items: Use _prepend suffix (e.g., post_start_prepend = [...])
• Append items: Use _append suffix (e.g., post_start_append = [...])

Example:

# .vibe.toml (shared)
[hooks]
post_start = ["npm install", "npm run build"]

# .vibe.local.toml (local)
[hooks]
post_start_prepend = ["echo 'local setup'"]
post_start_append = ["npm run dev"]

# Result: ["echo 'local setup'", "npm install", "npm run build", "npm run dev"]

Note: post_clean hooks are appended to the removal command with &&, executing in the main repository directory after the git worktree remove command completes.

Vibe displays a real-time progress tree during hook execution to show task status. Hook output is handled differently depending on the context:

• When progress display is active: Hook stdout is suppressed to keep the progress tree clean and avoid visual clutter. Only the progress tree is shown.
• When progress display is not active: Hook stdout is written to stderr (to avoid interfering with shell wrapper eval).
• Failed hooks: stderr output is ALWAYS shown regardless of progress display, to help with debugging.

Example progress display:

✶ Setting up worktree feature/new-ui…
  ⎿  ☒ Pre-start hooks
       ⎿  ☒ npm install
          ☒ cargo build --release
     ⠋ Copying files
       ⎿  ⠋ .env.local
          ☐ node_modules/

Note: Progress display auto-disables in non-TTY environments (e.g., CI/CD), and hook output will be shown normally.

The following environment variables are available in all hook commands:

See CONTRIBUTING.md for development setup and guidelines.

Apache-2.0