subagent-worktree-isolation-makes-changes-vanish
Passing isolation: "worktree" to Agent dispatches writes changes to a temp git worktree, not the live tree. The orchestrator receives a diff but changes are never applied to production files. Never use isolation: "worktree" for production execution work; reserve it only for actual experimentation.
Related
- clawteam-openclaw-multi-agent-swarm-evaluation
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- docker
- oracle-stack-is-multi-layer-platform-not-just-autoresearch-s
- nova-orchestration-model-for-cios-agents
- subagent-type-general-purpose-required-for-execution
- subagent-stall-root-causes-and-fixes
- isolation-worktree-never-for-production-subagents
- isolation-worktree-makes-subagent-changes-vanish
- subagent-dispatch-contract-general-purpose-only
- subagent-worktree-isolation-destroys-live-changes
- isolation-worktree-subagent-changes-not-applied-to-live
- isolation-worktree-causes-subagent-changes-to-vanish