When forwarding your machine's hooks to a cloud session (claude --cloud), each hook is now checked for whether its script or its config file sits somewhere the cloud session could itself write to. Hooks that cannot be pinned, because they are not a single script, are unreadable, hard-linked or oversized, or live inside the checkout, get a notice saying so and are not run. Successful registrations went quiet.
- The routine registration summary and the "this window now runs your hooks" line dropped from info to debug level.
- No separate flag; this applies on the cloud hook forwarding path.
is not a single script this machine can pin, so it is not run for the cloud session from this machine
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.
| `CCR_FORCE_BUNDLE` | Set to `1` to force [`claude --cloud`](/docs/en/claude-code-on-the-web#send-local-repositories-without-github) to bundle and upload your local repository instead of cloning from its remote |env-vars see the edit
`--cloud` works with a single repository at a time. The task runs in the cloud while you continue working locally. The older `--remote` spelling still works as a deprecated alias for `--cloud`.claude-code-on-the-web see the edit
Anthropic's documentation has since written up --cloud, on Use Claude Code on the web.