{"version":"2.1.323","anchor":"git-network-watchdog-tracks-a-floor-budget","canonical_anchor":"git-network-watchdog-tracks-a-floor-budget","heading":"Git network timeout changes how it counts silent time","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/git-network-watchdog-tracks-a-floor-budget","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Git network timeout changes how it counts silent time\n\nThe timer that stops a stalled git network operation now keeps a separate time budget while only the server is reporting progress\n\n**Unclear.** It is unclear whether slow git operations will now be stopped sooner or later than before.\n\n**What**\n\nClaude Code watches git network operations, such as a clone, and stops them if they go quiet for too long. That timer now keeps a separate time budget while only the server is reporting progress. The message about the limit before any transfer starts now appears only when that limit is at least as long as the allowed silent time.\n\n**Why**\n\nThis affects when a slow clone gets stopped.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}