{"version":"2.1.295","anchor":"git-clone-watchdog-pre-transfer-cap-and-server-side-progres","canonical_anchor":"git-clone-watchdog-pre-transfer-cap-and-server-side-progres","heading":"Stuck git clones now report whether the server stalled or a time cap was hit","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/git-clone-watchdog-pre-transfer-cap-and-server-side-progres","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Stuck git clones now report whether the server stalled or a time cap was hit\n\nGit's stuck-clone check now watches server-side progress before data arrives, has a time cap, and names the cause when it stops git\n\n**What**\n\nWhen 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.\n\nIt 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.\n\nWhen git is stopped, the message now gives the reason:\n\n- The pre-transfer cap was reached before any data arrived.\n\n- Server-side progress stopped advancing.\n\n**Why**\n\nSome 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.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}