A Git worktree manager for coding agents.
ket gives each task a branch, a working directory and an agent session, and leaves your main checkout alone.
Start from the project you already have
Add a project once, then create a worktree for each task. The worktree has its own branch and files, so an agent can work there while your base checkout stays where you left it.
ket keeps worktrees outside your repository, in ~/.local/share/ket/worktrees/, so they never show up as untracked files in your checkout. ket names each folder after its branch, with a short hash so no two collide.
Up to date when it starts
A new worktree starts from the project's base branch unless you pick another. ket fetches the remote first: if the remote branch is ahead, the worktree starts from it, and ket fast-forwards your local branch when that loses nothing. If the fetch fails, ket carries on from your local branch.
Ready to build and test
A fresh checkout has no node_modules, virtual environment or .env file, so an agent's first build would fail. ket's provisioning brings them across from your primary checkout: it clones node_modules, .venv and vendor, skips target, and copies .env, .env.local and .env.*.local, never writing their contents to a log. You can change the list per repository.
On macOS the clone is copy-on-write: the copy shares the original's data on disk until something changes, and ket falls back to a normal copy where that isn't available. On one Mac, cloning a 20,000-file, 78 MB folder this way took 293 ms; your time depends on the folder and the disk.
ket worktree add provisions every worktree it creates. ket doesn't provision worktrees made in the app, from the Create worktree dialog, the quick prompt, the backlog or a phone, until you run Re-run provisioning for a worktree from the command palette. Getting a worktree ready for an agent covers what provisioning doesn't, such as ports and databases.
Keep concurrent changes separate
With separate worktrees, no two tasks share a working directory. Each session stays attached to its task, and ket shows its state, changed files and diff, so you don't piece that context together from terminal tabs.
Review before the merge
Read the uncommitted changes or compare the full branch with its base. When the work is ready, ket shows what it will commit and runs the commit and merge from the same workspace. It merges into the base branch in your primary checkout, and never switches that checkout's branch for you.
Learn more
Worktrees in the docs covers naming, provisioning settings and deleting a worktree. If worktrees are new to you, start with the Git worktree tutorial.