Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Cloud session seeding refuses a symbolic git HEAD; sandbox and device checks tightened

Cloud sessions reject a git HEAD on a symbolic ref and suggest git switch, alongside sandbox config and untrusted-device enrollment tweaks

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

What

When you start a cloud session, Claude Code copies ('seeds') your git repository into it. Seeding now refuses a repository whose current position (HEAD) is checked out under a symbolic ref, meaning a second name that points at another branch. The error is symbolic_head, and it comes with a hint to use git switch to move to the branch by its own name. Seeding also now checks the working files before it rebuilds its cached copy of the repository.

Other changes in the same area:

  • Sandbox settings now keep track of symlink permissions granted later and of blocked folders. The sandbox is a walled-off area that limits what commands can touch. A symlink is a shortcut that points to another file or folder.
  • In managed mode, ignoreViolations and the options that allow a weaker nested sandbox or weaker network isolation are now combined through a shared merge step.
  • When a request is refused with a 403 error because the device is not trusted, Claude Code now checks whether cloud sessions or Remote Control should enroll the device before trying to recover. Before, it always tried to recover.

Why

If a cloud session will not start and mentions a symbolic ref, switch to your branch by name with git switch and try again. The other changes tighten how the sandbox and device trust are handled.

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 doubtIt is not clear what condition decides when the administrator-managed merging applies.

See this entry in the whole of v2.1.285 →

Feedback