Summary
The dispatch documentation (https://bassimeledath-dispatch.mintlify.app/introduction) clearly shows worktree execution as a first-class feature:
"security audit the auth flow... use opus, do it in a worktree"
"Five workers, three models, three worktrees."
However, the current SKILL.md contains zero mentions of worktree. There are no dispatcher instructions for handling the worktree directive in user prompts.
Observed behavior
When dispatching tasks with worktree specified (e.g. "implement X — sonnet, worktree"), the dispatcher receives no guidance on what to do. In my session it silently fell back to creating a regular git branch instead — the directive was ignored without any warning to the user.
Expected behavior
When a user specifies worktree for a task, the dispatcher should:
- Call
EnterWorktree (available as a Claude Code tool) to create an isolated git worktree directory
- Spawn the worker with the worktree path as its working directory (instead of
$(pwd))
- After completion, merge the branch and call
ExitWorktree
The EnterWorktree / ExitWorktree tools are already available in Claude Code's deferred tool set, so the infrastructure exists — it just needs to be wired into the SKILL.md dispatcher instructions.
Impact
Users who rely on worktree for filesystem-level isolation (parallel workers writing to separate directories without conflicts) currently get no isolation at all. This is especially important for parallel tasks that touch the same files.
Environment
- Host: Claude Code (claude-sonnet-4-6)
- Platform: macOS Darwin 25.3.0
Summary
The dispatch documentation (https://bassimeledath-dispatch.mintlify.app/introduction) clearly shows worktree execution as a first-class feature:
However, the current SKILL.md contains zero mentions of
worktree. There are no dispatcher instructions for handling theworktreedirective in user prompts.Observed behavior
When dispatching tasks with
worktreespecified (e.g."implement X — sonnet, worktree"), the dispatcher receives no guidance on what to do. In my session it silently fell back to creating a regular git branch instead — the directive was ignored without any warning to the user.Expected behavior
When a user specifies
worktreefor a task, the dispatcher should:EnterWorktree(available as a Claude Code tool) to create an isolatedgit worktreedirectory$(pwd))ExitWorktreeThe
EnterWorktree/ExitWorktreetools are already available in Claude Code's deferred tool set, so the infrastructure exists — it just needs to be wired into the SKILL.md dispatcher instructions.Impact
Users who rely on
worktreefor filesystem-level isolation (parallel workers writing to separate directories without conflicts) currently get no isolation at all. This is especially important for parallel tasks that touch the same files.Environment