{"version":"2.1.281","anchor":"git-subprocesses-get-git-trace2-output-turned-off-by-default","canonical_anchor":"git-subprocesses-get-git-trace2-output-turned-off-by-default","heading":"Git subprocesses get GIT_TRACE2 output turned off by default","tier":"notice","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/git-subprocesses-get-git-trace2-output-turned-off-by-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Git subprocesses get GIT_TRACE2 output turned off by default\n\nGit commands run by Claude Code now have GIT_TRACE2 tracing turned off by default, unless you have set those variables yourself\n\n**What**\n\nWhen Claude Code runs git, it now sets several environment variables that switch off git's built-in trace logging. Environment variables are named values a program reads when it starts:\n\n- `GIT_TRACE2`, `GIT_TRACE2_EVENT` and `GIT_TRACE2_PERF` are set to \"0\".\n\n- `GIT_TRACE2_MAX_FILES` is set to \"0\".\n\n- The trace variables covering environment and config parameters are set to \"-\".\n\nIf you have already given any of these a non-empty value, your value is kept.\n\n**Why**\n\nGit commands started by Claude Code no longer produce trace output by default. You can still turn tracing on by setting these variables yourself.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}