isolation-worktree-never-for-production-subagents
Agent tool’s isolation:worktree parameter creates a temporary git worktree; all writes go to that isolated copy and return as a diff that the orchestrator must manually re-apply. For production work where subagents should directly modify the live codebase, omit isolation:worktree entirely. Reserve worktree mode only for experimental branches where you explicitly want a clean test baseline with no live-tree side effects.
Related
- subagent-worktree-isolation-makes-changes-vanish
- subagent-stall-root-causes-and-fixes
- clawteam-openclaw-multi-agent-swarm-evaluation
- docker
- oracle
- isolation-worktree-makes-subagent-changes-vanish
- subagent-worktree-isolation-destroys-live-changes
- isolation-worktree-subagent-changes-not-applied-to-live