Quick Start

This guide walks you through the core daft workflow: cloning a repo, creating branches, and cleaning up.

1. Clone a Repository

daft clone git@github.com:user/my-project.git

This creates a structured layout:

my-project/
├── .git/           # Shared Git metadata
└── main/           # Worktree for the default branch
    └── ... (project files)

You're automatically placed in my-project/main/.

This shows the contained layout. daft supports other layouts that

organize worktrees differently — see Layouts to explore your options. :::

2. Create a Feature Branch

From anywhere inside the repository:

daft start feature/auth

This creates a new branch and worktree in one step:

my-project/
├── .git/
├── main/               # Default branch (untouched)
└── feature/auth/       # New branch with its own worktree
    └── ... (project files)

You're now in my-project/feature/auth/. Your main/ directory is completely untouched.

3. Switch Between Branches

Each branch is just a directory. Open different terminals:

# Terminal 1 - working on feature
cd my-project/feature/auth/
npm run dev

# Terminal 2 - checking main
cd my-project/main/
npm test

To check out an existing branch:

daft go bugfix/login-issue

4. Branch From Default

When you need a fresh branch from main (regardless of where you are), use the gwtcbm shortcut from shell integration:

daft start hotfix/critical-fix main

# Or with the gwtcbm shortcut (from shell integration)
gwtcbm hotfix/critical-fix

Your directory structure becomes:

my-project/
├── .git/
├── main/
├── feature/auth/
├── bugfix/login-issue/
└── hotfix/critical-fix/    # Branched from main, not current branch

5. Carry Changes Between Worktrees

Move uncommitted work to another worktree:

# Move changes from current worktree to feature/auth
daft carry feature/auth

# Or copy changes (keep them in both places)
daft carry --copy feature/auth main

6. Clean Up Merged Branches

After branches are merged and deleted on the remote:

daft prune

This automatically:

• Fetches from remote and prunes stale tracking branches
• Identifies local branches whose remotes were deleted
• Removes associated worktrees
• Deletes local branches

7. Adopt an Existing Repository

Already have a traditional repository? Convert it:

cd my-existing-project
daft adopt

This restructures your repo into the worktree layout. Uncommitted changes are preserved.

Git-native commands Every daft command has a git-native equivalent

(e.g., daft clone = git worktree-clone). See the CLI Reference for the full list. :::

What's Next

• Shell Integration - Enable auto-cd into new worktrees
• Layouts - Choose how worktrees are organized on disk
• Worktree Workflow - Deep dive into the worktree-centric approach
• Hooks - Automate worktree lifecycle events
• Shortcuts - Enable short command aliases
• Configuration - Customize daft's behavior