{"version":"2.1.251","anchor":"what-the-confined-mode-changes-across-cloud-permissions-and-","canonical_anchor":"what-the-confined-mode-changes-across-cloud-permissions-and-","heading":"What the confined mode changes across cloud, permissions and plugin loading","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/what-the-confined-mode-changes-across-cloud-permissions-and-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### What the confined mode changes across cloud, permissions and plugin loading\n\nConfined mode also blocks cloud sessions and changes how MCP servers and hooks load.\n\n**What**\n\nThe same confined-evaluation flag also stops cloud and background session creation, restricts always-allow rules to command-line sources, alters file hard-link and settings-source checks, and changes how MCP servers and hooks are loaded.\n\n**Details**\n\n- Cloud session refusal surfaces as the reason `eval_confined`.\n- The flag is written by Claude Code when spawning its own subprocess, not read from user config.\n\n**Evidence**\n\n`eval_confined`\n\n- Area: Plugin Eval\n- Names: `CLAUDE_CODE_EVAL_CONFINED`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}