What
A tool driving a cloud session through the headless --cloud client now gets a 'cancelled' status, and only that status, for each queued command an interrupt with cancel_queued:true dropped, so it can tell that those commands will never run.
Details
- The cancellation messages follow the interrupt's own success response and are not ordered against the result of the turn that was interrupted.
- Identifiers you do not recognise may appear, because another client connected to the same session may have queued the prompt.
- Documented for the stdout stream in
-pand SDK sessions, headless--cloudclient only.
Evidence
A host driving a cloud-hosted session through the headless --cloud client also receives 'cancelled' (and only that state) after its interrupt with cancel_queued:true
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle--cloud
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.
Added since
A small documentation edit on Environment variables touched a line naming --cloud after this was published.
| `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
Confirmed since
Anthropic's documentation has since written up --cloud, on Use Claude Code on the web.
`--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
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --cloud, on Use Claude Code on the web.