{"version":"2.1.315","anchor":"git-subprocess-timeouts-moved-to-an-event-loop-tick-budget","canonical_anchor":"git-subprocess-timeouts-moved-to-an-event-loop-tick-budget","heading":"Git commands are stopped differently when they run too long","tier":"internal","area":"Git Integration","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/git-subprocess-timeouts-moved-to-an-event-loop-tick-budget","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Git commands are stopped differently when they run too long\n\nClaude Code's own git commands can now be cut off by a new timer or when their output grows too large, and report a timeout\n\n**What**\n\nClaude Code runs git commands in the background for its own use. In some cases it now stops them with its own countdown instead of a plain time limit. It also stops a command whose output grows past the allowed size, and in both cases the result is marked as timed out.\n\n**Why**\n\nThis changes how long-running git commands get cut off.\n\n- Area: Git Integration\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}