Cloud sessions withhold hooks they could change, ask consent earlier and reword hook warnings

What

A hook is a command of yours that Claude Code runs at a set moment, for example before Claude runs a command. When you start a cloud session with claude --cloud, Claude Code decides which of your local hooks the session may use.

• Hooks from files that the cloud session itself could change are now withheld. A notice per source says, for example, "Hooks from ... are not offered to the cloud session" because "the cloud session may change that file". Before, withheld hooks were not listed per source.
• Claude Code now asks for your consent before it records which hooks are in use. If you decline, it stops there and shows no hook notices.
• If hooks change in your local settings file, which the cloud session can write, the warning is shorter: "Hooks changed in ..., which the cloud session can write." It goes on to say "The change is ignored for this session. Check the file, then restart claude --cloud."
• Warnings for other sources no longer include the sentence about the session keeping the hooks it had when you launched.
• When a hook cannot be stored safely, the error now says Claude Code "couldn't save a private copy of it" instead of a "verified copy". The fix is unchanged: set CLAUDE_CODE_TMPDIR to a folder the session cannot write to.

Reporting worktree state during a cloud handoff stays behind the tengu_ccr_handoff_metadata switch. The flag server returned on for this site's account and for the anonymous baseline, but no reading has been taken under this release.

Why

This changes which local hooks run in a cloud session. A hook stored in a file the cloud session could edit is not used there, so the session cannot rewrite the checks meant to limit it. If a hook you expected is missing, the notices tell you which source was withheld.