You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release
What
Starting a cloud session (a Claude Code session that runs on remote machines) now gives clearer messages when it fails:
--tools on a self-hosted environment: the message now says "--tools does not work yet with the self-hosted environment".
Launches that need a session attached to this computer now get their own refusal message.
Missing sign-in: the message says cloud sessions need a claude.ai sign-in and suggests running claude auth login (or /login in a local session).
An empty repository that cannot be bundled up for the session now comes with advice.
A missing-object failure while saving your uncommitted changes suggests retrying and, if it stops again, running git fsck in the checkout.
Usage data now also records whether a self-hosted environment was involved.
Why
When a remote session will not start, the message now tells you what to do next.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeImproved the error shown when a cloud session is refused because your claude.ai login was rejected or has expired: it now tells you to sign…
