What
A cloud session now holds back your first message until the initial upload of your project files has actually landed on the server, instead of sending it against an empty or half-populated workspace. While waiting it prints progress lines, retries the first push on a backoff schedule, and if it never lands it stops with a "seed_incomplete" result. Reached on any claude --cloud session; no flag guards it.
Details
- The wait is implemented as a gate on the send manager, registered with
onRelease: "withhold", so queued input is held rather than dropped. - Retries only apply on the initial "create" upload, not on later incremental syncs.
- New telemetry
tengu_dir_sync_git_first_send_waitreportswaited_msand one ofwedged,released,withdrawn, orlanded.
Evidence
tengu_dir_sync_git_first_send_wait
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.