Worktrees

Kent can manage git worktrees for you. Creating or switching a worktree moves that session into the selected checkout and gives the agent necessary context. Managed worktrees are created according to config.toml’s [worktrees].base_dir, and Kent switches the session into the new worktree after create. Run /wt to get started.

Switch

<target> must resolve uniquely. Kent matches, in order:

• worktree id
• canonical path
• display name
• branch name
• main for the main workspace worktree

Delete

The main workspace worktree cannot be deleted. Deletion is blocked when another session targets that worktree or when background processes are running inside it.

Tip

If you delete the active worktree, Kent moves the session back to the main workspace without preserving file edits or commits.

Configuration

Since worktrees are basically raw git checkouts, you can set-up a custom worktree creation script that will prepare newly created checkouts with local data like .env, encryption credentials, gradle wrappers, installed dependencies, local skills/config, etc.

[worktrees]
base_dir = "~/.kent/worktrees"
# setup_script = "scripts/setup-worktree.sh"

• base_dir sets the root directory for Kent-managed worktrees.
• setup_script runs after creating a worktree in the background. Relative paths resolve from the workspace root.

The script receives environment variables as input:

• KENT_WORKTREE_SOURCE_WORKSPACE_ROOT - Original/main workspace root that created the worktree, e.g. /Users/user/Developer/app or C:\Users\user\dev\app.
• KENT_WORKTREE_BRANCH_NAME - Branch/ref name selected for the new worktree, e.g. feature/search-fix.
• KENT_WORKTREE_ROOT - Filesystem path to the newly created worktree; setup script runs with this as cwd, e.g. /Users/nek/.kent/worktrees/app/search-fix.
• KENT_WORKTREE_SESSION_ID - Kent session id that requested the worktree, e.g. b31234ab-78ce-43d1-8f4c-2d6c6d4adbc1.
• KENT_WORKTREE_PROJECT_ID - Kent project id for the workspace/project, e.g. project-94b18685-19ed-4513-96bb-bcffa10410ff.
• KENT_WORKTREE_WORKSPACE_ID - Kent workspace binding id for the source workspace, e.g. workspace-2f7b6d4a.
• KENT_WORKTREE_WORKTREE_ID - Kent metadata id for the created worktree, e.g. worktree-8c9a0e3f.
• KENT_WORKTREE_CREATED_BRANCH - Whether Kent created a new branch for this worktree, e.g. true or false.
• KENT_WORKTREE_PAYLOAD_JSON - Full setup payload as one JSON string containing all fields above, e.g. {"source_workspace_root":"/repo","branch_name":"feature/x","worktree_root":"/repo-wt","session_id":"...","project_id":"...","workspace_id":"...","worktree_id":"...","created_branch":true}.

It also receives JSON as stdin:

{
    "source_workspace_root": "/path/to/main/workspace",
    "branch_name": "feature/name",
    "worktree_root": "/path/to/new/worktree",
    "session_id": "...",
    "project_id": "...",
    "workspace_id": "...",
    "worktree_id": "...",
    "created_branch": true
}