Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.251 Home All releases ←olderv2.1.250
Claude Code v2.1.251

Clearer error when a cloud session cannot clone from GitLab or Bitbucket

You'll notice
Useful3 Signal3
Cloud Sessions

Cloud sessions now say plainly that GitLab and Bitbucket repos can't be cloned yet.

What

Trying to move a GitLab or Bitbucket repo into a cloud session now says plainly that cloud sessions cannot clone from that host yet, instead of only pointing you at GitHub setup steps.

Details
  • The message names the detected host rather than assuming GitHub.
  • It appears on the non-GitHub path when no usable git source is available for the repo.
Evidence

Cloud sessions can't clone from ${vn} yet

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.251 →