# Create a worktree with an auto-generated name
codebuddy --worktree

# Create a worktree with a specified name
codebuddy --worktree feature-auth

# Create a worktree with a specified base branch
codebuddy --worktree --worktree-branch origin/develop  # Based on the remote develop branch
codebuddy --worktree --worktree-branch feature/foo     # Based on the local feature/foo branch

# Run in a tmux session (recommended for long-running tasks)
codebuddy --worktree --tmux

# Create a worktree based on a PR/MR (for code review)
codebuddy --worktree "#123"                                    # GitHub PR number
codebuddy --worktree "https://github.com/owner/repo/pull/123" # GitHub PR link
codebuddy --worktree "https://gitlab.com/owner/repo/-/merge_requests/456" # GitLab MR link
codebuddy --worktree "https://cnb.woa.com/owner/repo/-/pulls/789" # CNB PR link

> start a worktree
> work in a worktree
> Start a worktree

{
  "worktree": {
    "symlinkDirectories": ["node_modules", ".next", ".cache", "dist"]
  }
}

# .worktreeinclude
# List local files to copy to the new worktree

# Environment variables
.env.local
.env.development.local
.env.test.local

# Local IDE configuration
.vscode/settings.json

# Local certificates or keys (if any)
certs/localhost.pem

1. Is a WorktreeCreate hook configured? → Use the hook to create (the hook is preferred even in Git repositories).
2. In a Git repository? → Use git worktree.
3. None of the above? → Report an error and prompt to configure a hook.

{
    "hooks": {
        "WorktreeCreate": [
            {
                "hooks": [
                    {
                        "type": "command",
                        "command": "bash ~/.codebuddy/hooks/worktree-create.sh"
                    }
                ]
            }
        ],
        "WorktreeRemove": [
            {
                "hooks": [
                    {
                        "type": "command",
                        "command": "bash ~/.codebuddy/hooks/worktree-remove.sh"
                    }
                ]
            }
        ]
    }
}

{
    "hook_event_name": "WorktreeCreate",
    "session_id": "abc123def456",
    "cwd": "/Users/user/project",
    "transcript_path": "/Users/user/.codebuddy/sessions/abc123/transcript.md",
    "name": "feature-auth"
}

{
    "hook_event_name": "WorktreeRemove",
    "session_id": "abc123def456",
    "cwd": "/Users/user/project",
    "transcript_path": "/Users/user/.codebuddy/sessions/abc123/transcript.md",
    "worktree_path": "/tmp/codebuddy-worktrees/feature-auth"
}

# Correct example: logs are output to stderr, and the path is output to stdout.
echo "Initializing SVN checkout..." >&2
echo "/home/user/.codebuddy/worktrees/feature-auth"

#!/bin/bash
set -e

INPUT=$(cat)
NAME=$(echo "$INPUT" | jq -r '.name')
CWD=$(echo "$INPUT" | jq -r '.cwd')

WORKTREE_PATH="$HOME/.codebuddy/worktrees/$NAME"
mkdir -p "$WORKTREE_PATH"

# Add VCS initialization logic here (SVN checkout, P4 sync, directory copy, etc.)
cp -r "$CWD"/* "$WORKTREE_PATH/" 2>/dev/null || true

# Output the absolute path to stdout on the last line (required)
echo "$WORKTREE_PATH"

#!/bin/bash

INPUT=$(cat)
WORKTREE_PATH=$(echo "$INPUT" | jq -r '.worktree_path')

# Security check: ensure the path is within the expected range.
if [[ "$WORKTREE_PATH" != "$HOME/.codebuddy/worktrees/"* ]]; then
    echo "Refusing to remove path outside worktrees directory: $WORKTREE_PATH" >&2
    exit 1
fi

rm -rf "$WORKTREE_PATH"

{
    "hooks": {
        "WorktreeCreate": [
            {
                "hooks": [
                    {
                        "type": "command",
                        "command": "bash -c 'INPUT=$(cat); NAME=$(echo $INPUT | jq -r .name); DIR=\\"$HOME/.codebuddy/worktrees/$NAME\\"; svn checkout https://svn.example.com/repo/trunk \\"$DIR\\" >&2 && echo \\"$DIR\\"'"
                    }
                ]
            }
        ],
        "WorktreeRemove": [
            {
                "hooks": [
                    {
                        "type": "command",
                        "command": "bash -c 'cat | jq -r .worktree_path | xargs rm -rf'"
                    }
                ]
            }
        ]
    }
}

{
    "hooks": {
        "WorktreeCreate": [
            {
                "hooks": [
                    {
                        "type": "command",
                        "command": "bash -c 'INPUT=$(cat); NAME=$(echo $INPUT | jq -r .name); CWD=$(echo $INPUT | jq -r .cwd); DIR=\\"$HOME/.codebuddy/worktrees/$NAME\\"; cp -r \\"$CWD\\" \\"$DIR\\" && echo \\"$DIR\\"'"
                    }
                ]
            }
        ],
        "WorktreeRemove": [
            {
                "hooks": [
                    {
                        "type": "command",
                        "command": "bash -c 'cat | jq -r .worktree_path | xargs rm -rf'"
                    }
                ]
            }
        ]
    }
}

# Basic Usage
codebuddy --worktree --tmux

# Use traditional mode (without popup)
codebuddy --worktree --tmux --tmux-classic

your-repo/
├── .codebuddy/
│   └── worktrees/
│       ├── feature-auth/      # worktree directory
│       │   ├── node_modules -> ../../node_modules  # symbolic link
│       │   └── ...
│       └── fix-bug-123/
├── .worktreeinclude           # Defines local files to copy (recommended to commit)
└── ...

# View all current worktrees
git worktree list

# Delete a specified worktree (when there are no uncommitted changes in the worktree)
git worktree remove .codebuddy/worktrees/feature-auth

# Force delete (when there are uncommitted changes)
git worktree remove --force .codebuddy/worktrees/feature-auth

# Also delete the corresponding branch
git branch -D worktree-feature-auth

# Clean up stale worktree references (the directory is deleted but Git still tracks it)
git worktree prune

# Create a new branch and a worktree (outside the repository)
git worktree add ../project-feature-a -b feature-a

# Check out an existing branch
git worktree add ../project-bugfix bugfix-123

# Enter the worktree and start CodeBuddy Code
cd ../project-feature-a && codebuddy

# Clean up after use
git worktree remove ../project-feature-a

---
name: isolated-worker
description: Work in a separate worktree without affecting the main repository.
isolation: worktree
---

You are running in a separate git worktree.
Focus on completing the task assigned to you, and report the results when done.

> Use the isolated-worker agent to create test.txt in the current directory and write "hello" to it.

# This file does not exist in the main repository.
ls test.txt
# → No such file or directory ✓

# The file is in the subagent's worktree.
ls .codebuddy/worktrees/agent-xxx/test.txt
# → Exists ✓

# Create a worktree based on the remote develop branch
codebuddy --worktree feature-xxx --worktree-branch origin/develop

# Create based on the local branch (preserving local unpushed commits)
codebuddy --worktree feature-yyy --worktree-branch my-local-branch

# Terminal 1: Continue developing the new feature
codebuddy --worktree feature-payment

# Terminal 2: Dedicated to fixing bugs without interfering with each other
codebuddy --worktree hotfix-login-crash

codebuddy --worktree refactor-esm

> Help me migrate the src/core directory from CommonJS to ESM

codebuddy --worktree "#456"

> Help me review what this PR changed and whether there are any potential issues.
> Run the tests

codebuddy --worktree task-docs --tmux
codebuddy --worktree task-tests --tmux
codebuddy --worktree task-new-api --tmux

> Use three parallel api-worker subagents:
  First, process the src/api/user/ directory.
  Second, process the src/api/order/ directory.
  Third, process the src/api/product/ directory.

git worktree remove --force .codebuddy/worktrees/my-feature
git branch -D worktree-my-feature
codebuddy --worktree my-feature

git worktree remove --force .codebuddy/worktrees/<name>
git branch -D worktree-<name>