Cloud sessions include the running process environment when deciding which hooks this machine offers.
What's wrong with this entry?
When a cloud session works out which hooks this machine offers, it now also takes the current process environment into account when building the shell prefix's own environment, alongside the environment attached to the session and the one captured before settings loaded. Only applies when hook consent is set to cloud; the user-facing explanations are unchanged.
All hooks were switched off in your settings during this cloud session; for it, this machine keeps offering the hooks it had when you launched (listed here) until you restart claude --cloud.
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