Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Moving a session to the cloud handles GitHub branch checks differently

When moving a session to a cloud session, branch checks can ask GitHub, and the no-shared-history message now names the remote's default branch

You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release

Unclear Whether the new branch lookup path runs at all, since its condition is switched off in this build.

What

When Claude Code moves a session to run in the cloud, it checks which git branch the cloud session should start from. Several things changed:

  • Branch checks can now always ask GitHub.
  • There is a new option to resync when the branch could not be worked out.
  • The message shown when your branch shares no history with the remote now names the remote's default branch.
  • The log line saying GitHub has no such branch is shorter.
Why

This affects which branch a cloud session starts from.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the new branch lookup path runs at all, since its condition is switched off in this build.

See this entry in the whole of v2.1.318 →

Feedback