The cloud device-hooks bridge gains a muted phase that unregisters from the cloud session and restores registration on unmute.
The cloud device-hooks bridge used by claude --cloud now supports a distinct muted phase, separate from stopped, idle, and registered. A new servingMute method transitions the bridge into {kind:"stopped", reason:"muted"}, unregisters and releases the current registration with the cloud session, and logs a muted outcome; unmuting restores registration and clears the muted note.
The device-hooks client-register flow also recognizes muted as an outcome alongside registered, unregistered, dormant, and no_consent, routed through the same success-telemetry path, with a servingMuted flag threaded through to consumers. Plugin-forwarding feature status reporting now reports muted state as { state: "off", source: "stored", reason: "muted" }, distinct from declined, unreadable, or could_not_send.
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
When you run `claude --cloud` from a repository that has no git remote, or from a github.com repository that the Claude GitHub App isn't installed on, Claude Code bundles your local repository and uploads it directly to the cloud session. …claude-code-on-the-web see the edit
Anthropic's documentation has since written up claude --cloud, on Use Claude Code on the web.