{"version":"2.1.268","anchor":"directory-sync-now-verifies-git-config-wasnt-mutated-mid-re","canonical_anchor":"directory-sync-now-verifies-git-config-wasnt-mutated-mid-re","heading":"Directory-sync now verifies git config wasn't mutated mid-read before trusting it","tier":"notice","area":"Git Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/directory-sync-now-verifies-git-config-wasnt-mutated-mid-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Directory-sync now verifies git config wasn't mutated mid-read before trusting it\n\nDirectory-sync now detects if git config changed while being read and refuses to trust it\n\n**What**\n\nWhen Claude Code's directory-sync feature decides whether it's safe to run git in a synced checkout, it now takes a fingerprint of each git config file (its device, inode, size, and change time, plus a hash for small files, following symlinks) both before and after reading it. If the fingerprint changed during the read, or a follow-up check shows the config changed since it was read, Claude Code now refuses to run git there rather than trusting a config that might have been altered mid-read.\n\n**Why**\n\nThis guards against acting on a git configuration that was modified while it was being read, which could otherwise lead to running git with stale or tampered settings.\n\n- Area: Git Safety\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}