Skip to content

Git & worktree problems

Why an AIgency task might fall back to the shared workspace instead of an isolated worktree, and how to fix it.

AgentDock Pro

Git worktree support only exists inside AIgency's task execution — it isn't a general-purpose workspace feature. See Git worktrees.

Task falls back to the shared workspace

AIgency only gives a task its own isolated worktree when the workspace-mode preference is 'worktree', or 'auto' combined with the run's global concurrency greater than 1. Even then, AgentDock always falls back to the shared workspace rather than blocking the task when:

  • The workspace folder isn't a Git repository.
  • Worktree creation fails for any reason (permissions, disk space, an existing conflicting branch, etc.).

If you expected task isolation and it isn't happening, check:

  1. That the workspace's project folder is actually a Git repository (git status succeeds in it).
  2. The Git executable AgentDock is using — Settings → Advanced → gitExecutablePath (defaults to git on PATH).
  3. The run's workspace-mode preference and global concurrency setting for that task.

Branch and worktree naming

AIgency creates worktrees under <project>/.aigency-worktrees/<runId8>/<taskId> on branches named aigency/<runId8>/<taskId8>-<slug>. If you see leftover branches or worktree folders after a run, they should be cleaned up automatically when the task or run is deleted — if they persist, check for a failed cleanup and remove them manually with git worktree remove and git branch -d.

Related