How does the Agent Teams plugin interact with worktrees?

[atirutw]

Do teammates work in one worktree, or can they do independent works in their own worktrees?

[ZYZ666-RGB]

Teammates are ordinary subagent Sessions under the Team Lead, not a worktree-per-member abstraction. Agent Teams coordinates a shared task board; it does not create or assign Git worktrees.

By default they work in the same checkout. If you omit cwd when starting a child, the new Session inherits the parent's effective directory at start time. After that, a working-directory change is local to that Session — it does not move teammates, and it is not a new Git worktree. Task writeScopes are advisory path prefixes, not locks, so overlap is warned rather than excluded.

Independent checkouts are possible, but only if the experimental Change requests & worktrees / create_worktree path is enabled. That tool creates a new branch and checkout, then switches the calling Session into it. It does not automatically give each teammate its own worktree. A teammate would need to call it (or be started with an explicit cwd) to work in a separate tree.

Docs that cover this:

• Agent Teams — shared board and advisory writeScopes
• Subagents — optional cwd, otherwise inherit the parent directory at start
• Working directory — changes are local to one Session
• Git worktrees — experimental create_worktree applies to the calling Session only