{"version":"2.1.239","anchor":"plugin-and-hook-forwarding-now-decided-at-startup-cloud-work","canonical_anchor":"plugin-and-hook-forwarding-now-decided-at-startup-cloud-work","heading":"Plugin and hook forwarding now decided at startup, cloud workers only","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/plugin-and-hook-forwarding-now-decided-at-startup-cloud-work","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Plugin and hook forwarding now decided at startup, cloud workers only\n\nTwo new environment variables let you refuse plugin or hook forwarding to a device.\n\n**What**\n\nStartup computes two decisions about whether this process may forward plugins and hooks to a device. Both admit only for a managed cloud worker, and two new environment variables, `CLAUDE_CODE_DISABLE_PLUGIN_FORWARDING` and `CLAUDE_CODE_DISABLE_HOOK_FORWARDING`, each force a refusal.\n\n**Details**\n\n- Managed cloud worker means an SDK URL and a remote session id are set, no environment kind is set, the entrypoint is allowlisted, and the run is not hermetic.\n- Refusing plugin forwarding because the environment variable is set logs an event named `plugin_forwarding_worker_disabled`.\n\n**Evidence**\n\n`plugin_forwarding_worker_disabled`\n\n- Area: Plugins\n- Names: `CLAUDE_CODE_DISABLE_PLUGIN_FORWARDING`, `CLAUDE_CODE_DISABLE_HOOK_FORWARDING`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}