{"version":"2.1.239","anchor":"git-runs-in-synced-directories-under-a-hardened-verified-lay","canonical_anchor":"git-runs-in-synced-directories-under-a-hardened-verified-lay","heading":"Git runs in synced directories under a hardened, verified layout","tier":"notice","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/git-runs-in-synced-directories-under-a-hardened-verified-lay","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Git runs in synced directories under a hardened, verified layout\n\nGit inside synced directories runs under a hardened layout with filters, hooks and protocols locked down.\n\n**What**\n\nBefore running git inside a synced directory, Claude Code reads the repository layout and checks it against the filesystem, pins off filter programs and hooks, restricts which protocols git may use, and disables lazy fetch, replace refs and grafts. Git is refused outright if a config file inside the working tree contributes settings, or if the git directory is not where git says it should be. Outcomes are recorded as telemetry.\n\n**Details**\n\n- Aimed at repositories synced from elsewhere, where the checked-out files could otherwise redirect git into running repo-supplied commands.\n\n**Evidence**\n\n`tengu_dir_sync_git_layout`\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}