Cloud-supplied hook scripts run through a vetted python3 wrapper that rechecks their checksum.
A hardened template runner exists inside the disabled cloud hook-template path.
tengu_violin_wood Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.242: on
tengu_violin_amati Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.242: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.242. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new runner executes hook scripts supplied by the cloud session. It picks the first absolute interpreter it can vet from a fixed list, writes the script to a per-process directory, and runs it through a wrapper that re-reads the file, enforces a size cap and re-checks its SHA-256 before executing. A mismatch exits with code 86 and is reported as an integrity failure.
- The spawn clears environment variables matching
LD_,DYLD_,GCONV_PATH,PYTHONand sets onlyCLAUDE_PROJECT_DIR. It runs detached in its own process group, which is killed on timeout or abort. - Registration and upload require two account flags together,
tengu_violin_woodandtengu_violin_amati. If neither has been served yet the request answers "hook_forwarding_not_ready: feature flags not yet available; retry". - Policy settings that restrict hooks to plugins, disable customization, allow only managed hooks, or disable hooks entirely clear the registry first.
- None of these strings exist in 2.1.241.
device hook template integrity check failed:
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.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook