{"version":"2.1.285","anchor":"git-trace-env-vars-now-set-to-0-instead-of-empty","canonical_anchor":"git-trace-env-vars-now-set-to-0-instead-of-empty","heading":"Git tracing is now switched off explicitly for Claude Code's git commands","tier":"notice","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/git-trace-env-vars-now-set-to-0-instead-of-empty","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Git tracing is now switched off explicitly for Claude Code's git commands\n\nClaude Code now sets `GIT_TRACE2`, `GIT_TRACE2_PERF` and `GIT_TRACE2_EVENT` to \"0\" instead of empty when it runs git\n\n**What**\n\nWhen Claude Code runs git, it sets `GIT_TRACE2`, `GIT_TRACE2_PERF` and `GIT_TRACE2_EVENT` to \"0\" instead of an empty value. These environment variables control git's tracing output, and \"0\" turns it off.\n\n**Why**\n\nSome git versions can treat an empty value differently, while \"0\" reliably turns tracing off, so extra trace output is less likely to appear in git commands Claude Code runs.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}