{"version":"2.1.295","anchor":"git-commands-no-longer-throw-errors-returned-as-result","canonical_anchor":"git-commands-no-longer-throw-errors-returned-as-result","heading":"Failed git commands now return an error result instead of crashing","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/git-commands-no-longer-throw-errors-returned-as-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Failed git commands now return an error result instead of crashing\n\nWhen a git command Claude Code runs internally fails, it is now logged and returned as a failed result instead of thrown as an error\n\n**What**\n\nClaude Code runs git (the version control program) behind the scenes for some of its own work. When one of those git commands now fails in a way that would previously have thrown an error, Claude Code catches it, logs it and returns a failed result with exit code 1 and the error message.\n\n**Why**\n\nA git command going wrong is now treated as an ordinary failure rather than an error that stops whatever called it, so it is less likely to cause a crash.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}