CLAUDE_CODE_DISABLE_HOOK_FORWARDING
A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.239, including the newest one read.
Two new environment variables let you refuse plugin or hook forwarding to a device.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.239.
In the changelogs
9Releases whose published page names CLAUDE_CODE_DISABLE_HOOK_FORWARDING.
-
v2.1.293
Hook forwarding to a device is skipped on Windows or when switched off
Claude Code does not forward hooks to a device on Windows or when
CLAUDE_CODE_DISABLE_HOOK_FORWARDINGis set, and records when hooks are held backfound in this entry's text
-
v2.1.287
Incoming hook and plugin messages in remote sessions are now counted, not blocked
Claude Code now records whether incoming hook and plugin messages pass a sender check, but still lets them all through
found in this entry's text
-
v2.1.283
Remote Control no longer lets hooks and plugins through its inbound guard
Remote Control's inbound guard now always excludes hooks and plugins, and remote tools depend on two environment variables
found in this entry's text
-
v2.1.248
Forwarding plugins and hooks to remote sessions is gated, and now says why it is off
Forwarding your plugins and hooks into remote sessions stays off unless the server enables it.
found in this entry's text
-
v2.1.247
Session-channel messages from senders this session cannot verify are refused, dropped or trimmed
Session-channel messages from unverified senders are dropped, and untrusted settings changes get their plugin key stripped.
found in this entry's text
-
v2.1.242
Consent screen explaining what forwarding your hooks to a cloud session means
A consent screen explains what letting cloud sessions run your local hooks means.
found in this entry's text
-
v2.1.239
Plugin and hook forwarding now decided at startup, cloud workers only
Two new environment variables let you refuse plugin or hook forwarding to a device.
named in this entry, found in this entry's text
-
v2.1.239
Sync and hook-forwarding switches now survive into remote sessions
Seven more environment variables you export locally now carry into remote and worker processes.
named in this entry, found in this entry's text
-
v2.1.239
Device hook forwarding worker added, off behind two flags and a kill switch
Cloud sessions could register hooks that run on your device, blocked by two off flags.
named in this entry, found in this entry's text
First cited
2The earliest release whose published evidence quoted CLAUDE_CODE_DISABLE_HOOK_FORWARDING was v2.1.239, 21 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
60One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.