subagent-worktree-isolation-destroys-live-changes
Passing isolation: worktree to Agent dispatch writes all subagent changes to a temporary git worktree, not the live working tree — changes return as a diff that the orchestrator must manually re-apply, and are silently lost if not re-applied. Never use isolation: worktree for production execution tasks; reserve it only for genuine sandboxed experimentation. Always use subagent_type: general-purpose (Tools: *) for execution work.
Related
- isolation-worktree-makes-subagent-changes-vanish
- subagent-worktree-isolation-makes-changes-vanish
- subagent-stall-root-causes-and-fixes
- isolation-worktree-never-for-production-subagents
- subagent-dispatch-contract-general-purpose-only
- isolation-worktree-subagent-changes-not-applied-to-live
- isolation-worktree-causes-subagent-changes-to-vanish