The hooks settings schema gained an optional cloud field on each entry, taking "device" or "skip". Anything it does not recognise is read as "skip", so a settings file written by a newer version still loads instead of erroring.
cloud: "skip"holds the hook on this machine, reported with the reason "author_skip".cloud: "device"exempts a command hook that could not otherwise be pinned, but is not honoured when the entry lives in a file inside the checkout, and is ignored for after-edit hooks.- The surrounding forwarding path can still be refused by policy ("hook_forwarding_disabled: policy"), so this is a per-entry knob on an existing gated path, not a feature on its own.
@internal Where this hook may run when a cloud session is driven from this machine., @internal Where this hook may run when a cloud session is driven from this machine. 'skip': never offer it to cloud sessions; 'device' or omitted: offered (an HTTP hook has no script to pin). Applies to this entry only. An unrecognised value reads as 'skip' (the file still loads).
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.