{"version":"2.1.285","anchor":"git-pinned-to-a-safe-binary-with-old-git-and-volume-in-reac","canonical_anchor":"git-pinned-to-a-safe-binary-with-old-git-and-volume-in-reac","heading":"Directory sync needs git 2.32 or newer and warns about more setups","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/git-pinned-to-a-safe-binary-with-old-git-and-volume-in-reac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Directory sync needs git 2.32 or newer and warns about more setups\n\nDirectory sync now runs git with a cleaned environment, needs git 2.32 or newer, and gives new reasons when it cannot read git\n\n**Unclear.** How many setups actually run git through this cleaned, version-checked path is not clear.\n\n**What**\n\nDirectory sync now runs git with a cleaned environment, meaning it strips the environment variables git would otherwise pick up. It also needs git 2.32 or newer, because that version can be told to ignore your personal git configuration. If git is older, or its version cannot be read, sync reports that it \"is older than 2.32, or its version could not be read\".\n\nThere are new reasons sync gives when it cannot use git normally:\n\n- `volume_in_reach`, about a volume within the area sync covers\n\n- `old_git`, when git is older than 2.32\n\n- a case where your home directory is itself a git checkout\n\nThe usage report sent to Anthropic when git is not found on the starting path also records more details.\n\n**Why**\n\nIn cloud sessions, sync could skip reading git without saying so when git was too old. If you rely on it, check that your git is 2.32 or newer.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}