What
--print --cloud was previously refused as interactive-only. It now sends the prompt to an existing cloud session when you identify one, and the error tells you the accepted forms if you pass anything else.
Details
- Accepted identifiers: a session ID starting
session_orcse_, or a claude.ai/code URL. - Passing a bare description (to start a new session) still fails, and the message now says to drop
--printfor that. - A parallel message covers running without a terminal attached.
Usage
claude --print --cloud session_abc123 "summarise the failing test"Evidence
is not a cloud session ID or URL.
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.
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
Confirmed since
Anthropic's documentation has since written up --print, on Claude Code changelog.
* Fixed PermissionRequest hooks not firing in `--print` modechangelog 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 --print, on Claude Code changelog.