FAQ

Do I have to commit daft.yml to use daft?

No. Run daft install to create a daft.yml for your own use, then add it to your .git/info/exclude (or .gitignore if you don't mind it appearing in the repo's tracked file list). Daft treats the file as a visitor configuration: it stays out of git, but daft still propagates it between worktrees through your normal development workflow. See visitor configuration.

What happens to my visitor daft.yml when I delete a worktree?

Daft records what it wrote into each worktree (the file's seed) and compares the copy against it at removal time. An untouched copy is deleted with the worktree — even when the default branch's config has since moved on, removal never overwrites it. A copy you edited is real data: daft offers to consolidate it (a three-way merge that only moves your changes), refuses in scripts, or — when you force — discards it to <git-common-dir>/.daft/discarded/<branch>/ where you can recover it. The default branch's config is only ever written by an announced daft merge consolidation or an explicit daft file merge.

Where did my deleted worktree's daft file go?

Forced removals (daft remove -f, prune --force) stash refined untracked daft files under <git-common-dir>/.daft/discarded/<branch>/ before deleting the worktree. daft file merge likewise backs up the target under <git-common-dir>/.daft/backups/file-merge/ before writing it.

Does daft replace git?

No. daft sits next to git. Every daft command either calls into git or wraps a git operation. You can mix git and daft commands freely in the same repo.

Does daft work with monorepos?

Yes. See Recipes → Walkthroughs → Node monorepo with services for the recommended end-to-end pattern.

Does daft work on Windows?

Yes. The binary is shipped for Windows and tested in CI. Shell integration works in PowerShell, Git Bash, WSL, and Cmd (limited). See Shell integration.

Does daft replace lefthook?

Today: no — daft hooks are scoped to worktree lifecycle. The lefthook drop-in is on the roadmap (#468).

Does daft replace GitHub Actions?

No. daft hooks are local CI — they run on developer machines, before code reaches the central repo. GitHub Actions runs centrally, after code arrives. They're complementary: shift fast checks left into daft hooks; keep slow/secrets-bound checks in Actions.

How do I migrate an existing repo to daft?

daft adopt. See Adopting existing repos.

How do I uninstall daft from a repo?

daft eject. The repo is restored to a single-working-tree layout.

Is daft safe for collaborators who don't use it?

Yes. daft writes to .git/ and a single daft.yml (if you use hooks). Collaborators using plain git see normal behavior; they don't need to adopt daft.

How does daft handle uncommitted changes when removing a worktree?

daft remove prompts before destroying uncommitted work. Use --force to bypass.

Does daft modify global git config?

No, ever. daft only writes repo-local config and its own files. Your global git config is untouched.

Where are hooks trusted?

In your XDG state directory — by default ~/.local/state/daft/trust.toml on Linux, ~/Library/Application Support/daft/trust.toml on macOS, %LOCALAPPDATA%\daft\trust.toml on Windows.