Troubleshooting

This page covers general daft issues — install, layout, basic shell integration. For symptoms specific to hooks and recipes (warmup hangs, trust-prompt loops, env vars not propagating), see Troubleshooting recipes.

If your problem isn't listed here, run daft doctor first — it diagnoses common configuration issues automatically.

"command not found: daft"

daft is installed but not on PATH. Verify the install location (brew prefix avihut/tap/daft on macOS) is in your shell's PATH.

My shell doesn't cd into the new worktree

Shell integration isn't installed. See Shell integration for the eval line to add to your shell config.

"daft.yml is untrusted; refusing to run hooks"

A daft.yml was added or changed. Trust the new contents:

git daft-hooks trust

This is intentional — see Trust & security for why.

Hooks fire but I don't see their output

Job stdout/stderr is captured to log files in ~/.local/state/daft/logs/ (XDG state dir). Inspect with:

git daft-hooks log show

Worktree creation fails with "fatal: <branch> is already checked out"

The branch is checked out in a different worktree. Either remove the other worktree first (daft remove <branch>), or use a different branch name.

daft adopt says my repo "looks like it's already adopted"

The repo already has the daft layout. Use daft list to see existing worktrees, or daft eject to restore a single-working-tree layout if you want to start over.

I can't tell which worktree is which

daft list prints all worktrees. With --format json you get machine-readable output.

When in doubt

Run daft doctor. It diagnoses install, shell integration, layout health, and hook trust state.