Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.295 ·

Stuck git clones now report whether the server stalled or a time cap was hit

Git's stuck-clone check now watches server-side progress before data arrives, has a time cap, and names the cause when it stops git

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

When Claude Code runs git, it watches for a clone that has stopped making progress and stops it. Before this change it only watched progress on your side of the connection.

It now also follows the progress lines the server sends while it prepares data, before any data is transferred. That waiting phase has a time cap, set by the watchdog.preTransferCapMs option. The watcher also reads watchdog.silenceMs from its options.

When git is stopped, the message now gives the reason:

  • The pre-transfer cap was reached before any data arrived.
  • Server-side progress stopped advancing.
Why

Some servers spend a long time preparing a clone. This matters most in cloud sessions. A slow clone now waits for a bounded time and explains clearly why it was stopped.

See this entry in the whole of v2.1.295 →

Feedback