{"version":"2.1.260","anchor":"remote-agent-isolation-falls-back-to-worktree-when-unavailab","canonical_anchor":"remote-agent-isolation-falls-back-to-worktree-when-unavailab","heading":"Remote agent isolation falls back to worktree when unavailable","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/remote-agent-isolation-falls-back-to-worktree-when-unavailab","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Remote agent isolation falls back to worktree when unavailable\n\nRemote agent isolation now falls back to worktree or local when remote execution isn't available.\n\nWhen `isolation:'remote'` is requested for a spawned agent but remote execution isn't available, for example due to no claude.ai login, the feature gate being off, restricted mode, or no git root, Claude Code now logs the reason and falls back to `worktree` isolation, or runs the agent locally, instead of failing.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}