{"version":"2.1.299","anchor":"git-status-uses-no-optional-locks","canonical_anchor":"git-status-uses-no-optional-locks","heading":"Claude Code's git status check no longer competes with your git commands","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/git-status-uses-no-optional-locks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Claude Code's git status check no longer competes with your git commands\n\nClaude Code now runs `git status` with `--no-optional-locks`, so it does not compete with your own git commands for git's lock\n\n**What**\n\nWhen Claude Code runs `git status`, it now adds the `--no-optional-locks` flag. Git uses a lock file to stop two git commands from changing the same files at once. With this flag, Claude Code's check no longer competes with other git processes for that lock.\n\n**Why**\n\nYour own git commands are less likely to fail because the lock is already taken while Claude Code checks the repository.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}