{"version":"2.1.288","anchor":"remote-agent-isolation-can-be-disabled-by-a-setting","canonical_anchor":"remote-agent-isolation-can-be-disabled-by-a-setting","heading":"A setting can now turn off remote isolation for subagents","tier":"soon","area":"Subagents","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-agent-isolation-can-be-disabled-by-a-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### A setting can now turn off remote isolation for subagents\n\nThe `remoteAgentIsolationDisabled` setting now turns off remote isolation, alongside the existing `CLAUDE_CODE_REMOTE` check\n\n**Unclear.** It is not fully settled that this check is the one controlling remote isolation for subagents.\n\n**What**\n\nRemote isolation runs a subagent, a helper Claude starts for part of a task, in a separate cloud environment. Claude Code's check for offering it now also says no when the `remoteAgentIsolationDisabled` setting is set. Before, only `CLAUDE_CODE_REMOTE` turned it off. The option still also depends on the tengu_neapolitan gate, which is off unless it is switched on remotely.\n\n**Why**\n\nUsers and administrators now have a setting to opt out of remote isolation.\n\n- Flag `tengu_neapolitan`: Not enough to say (read for one account on one subscription tier against v2.1.288; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Subagents\n- Names: `remoteAgentIsolationDisabled`, `CLAUDE_CODE_REMOTE`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no\n- Present in the build but not switched on"}