{"version":"2.1.295","anchor":"cloud-agent-launch-refused-when-claude-code-restrict-persona","canonical_anchor":"cloud-agent-launch-refused-when-claude-code-restrict-persona","heading":"Cloud agents cannot be launched from a session that restricts personal config","tier":"notice","area":"Subagents","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cloud-agent-launch-refused-when-claude-code-restrict-persona","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Cloud agents cannot be launched from a session that restricts personal config\n\nWith `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG` set, launching a cloud agent is refused and you are told to use worktree isolation\n\n**What**\n\n`CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG` is a new environment variable (a setting given to a program from the shell) that limits what your own Claude Code files can do in a session. When it is set, Claude Code refuses to launch a cloud agent, a helper that runs the work on a remote machine. The error explains that the cloud session would not apply those limits, and it tells you to set isolation to `\"worktree\"` instead. A worktree is a separate copy of your project on your own machine.\n\n**Why**\n\nA restricted session can no longer quietly pass work to a cloud session that would ignore the restrictions.\n\n- Area: Subagents\n- Names: `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}