{"version":"2.1.295","anchor":"claude-code-restrict-personal-config-blocks-agent-defined-mc","canonical_anchor":"claude-code-restrict-personal-config-blocks-agent-defined-mc","heading":"Restricted sessions block your own agents' MCP servers and cloud launches","tier":"use","area":"Subagents","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/claude-code-restrict-personal-config-blocks-agent-defined-mc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Restricted sessions block your own agents' MCP servers and cloud launches\n\nWith CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG set, your own agents' MCP servers are skipped and launching an agent in the cloud is refused\n\n**What**\n\nWhen the environment variable `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG` is set, two things change for agents (helpers Claude can hand work to) that you defined in your own files:\n\n- MCP servers listed in the agent's own definition are skipped. MCP servers are outside programs that give Claude extra tools.\n\n- Launching an agent to run in the cloud, on a remote machine, fails with an error.\n\nThe permission mode used for agents run remotely can now also be limited so that it can only be narrowed, never widened.\n\n**Why**\n\nIn a locked-down session, agents you defined yourself cannot bring in their own tools or move work to a remote machine.\n\n- Area: Subagents\n- Names: `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}