{"version":"2.1.178","anchor":"agent-tool-isolation-remote-cloud-hosted-subagents","canonical_anchor":"agent-tool-isolation-remote-cloud-hosted-subagents","heading":"Agent Tool: isolation: \"remote\" \u2014 Cloud-Hosted Subagents","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178\/e\/agent-tool-isolation-remote-cloud-hosted-subagents","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178","markdown":"### Agent Tool: `isolation: \"remote\"` \u2014 Cloud-Hosted Subagents\n\n**What**\n\nThe Agent tool's `isolation` parameter now accepts `\"remote\"` in addition to `\"worktree\"`. This launches the agent in a remote cloud (CCR) environment, always as a background task.\n\n**Usage**\n\n`\/\/ In a skill or agent prompt instructing Agent tool use: isolation: \"remote\"` **Details** - Always runs in the background; you are notified when it completes - Remote agents run against the repository's default branch if the current local branch is not pushed to origin - Not available in all contexts: if CCR is unavailable, the tool reports `[remote agent] isolation:'remote' is unavailable` - A local agent context or no git root causes automatic fallback to other isolation modes **Evidence** Remote agent branch check (search for `\"[remote agent] local branch '\"`, `\"isolation:'remote' is unavailable\"`, `\"CLAUDE_CODE_REMOTE_SESSION_ID\"`)"}