Two new environment variables let you refuse plugin or hook forwarding to a device.
What's wrong with this entry?
Startup 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.
- 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.
- Refusing plugin forwarding because the environment variable is set logs an event named
plugin_forwarding_worker_disabled.
plugin_forwarding_worker_disabled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.247
Plugin forwarding now tells the cloud worker which directories it can reach
Both mention disable forwarding
-
v2.1.229
Repositories can declare that all hooks are off
Both mention disable hook
-
v2.1.242
Managed hook skip message now says SDK callback hooks still run
Both mention disable hook