Each hook entry in settings can now carry a cloud field. device offers that hook to a cloud session even when its script lives somewhere the session could write to or cannot be pinned to fixed contents; skip never offers it. Leaving it out keeps the default, where only pinned, unwritable command hooks are offered. An unrecognised value is read as skip.
- The setting applies only to that one hook entry in that one settings scope, not to hooks generally.
- The message that forwards a hook to a cloud session now carries a matching
author_opt_inflag recording that the hook was explicitly opted in. - The description of pinning changed: the machine re-verifies the script's bytes before every run, rather than capturing them once.
- Forwarding as a whole still depends on a server-side feature flag and on policy; when the flag is off, the reason reported is
hook_forwarding_disabled: flag_off.
'skip': never offer it to cloud sessions.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
| `ca_bundle` | string (absolute path) | unset | PEM file added to the app's default TLS trust for sign-in, the Claude API, Anthropic-hosted connectors, update checks, and [cloud storage](/docs/claude-science/cloud-storage) access from Set…claude-science/configuration-file-reference see the edit
A Windows update released September 8, 2026 (including KB5124008) stops Cowork from reaching your files when it runs on your Windows PC, so tasks fail or the workspace does not start. This affects Cowork on third-party inference deployment…cowork/changelog see the edit
A small documentation edit on Changelog touched a line naming cloud after this was published.