{"version":"2.1.311","anchor":"git-fetch-throttling-http-429-git-wrapper-classified-val","canonical_anchor":"git-fetch-throttling-http-429-git-wrapper-classified-val","heading":"Git fetch failures caused by rate limiting are now reported as throttling","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/git-fetch-throttling-http-429-git-wrapper-classified-val","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Git fetch failures caused by rate limiting are now reported as throttling\n\nWhen `git fetch` is refused for rate limiting, Claude Code now says it was throttled and waits longer before retrying\n\n**What**\n\nWhen Claude Code runs `git fetch` and it fails, it now checks whether the failure was throttling, meaning the server asked it to slow down. Two cases count:\n\n- the server answered with HTTP 429, the \"too many requests\" response\n\n- a wrapper program installed as `git` exited with code 75\n\nIf the last attempt fails this way, the error says the fetch was throttled on its last attempt instead of the general \"git fetch failed after N attempts\" message. Retries for these failures wait longer between attempts.\n\n**Why**\n\nA rate limit is now kept apart from a real fetch failure, so you can tell whether to wait or to fix something.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}