{"version":"2.1.248","anchor":"git-lookups-are-cached-and-no-git-is-told-apart-from-git-som","canonical_anchor":"git-lookups-are-cached-and-no-git-is-told-apart-from-git-som","heading":"Git lookups are cached, and \"no git\" is told apart from \"git somewhere we won't look\"","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/git-lookups-are-cached-and-no-git-is-told-apart-from-git-som","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Git lookups are cached, and \"no git\" is told apart from \"git somewhere we won't look\"\n\nGit lookups are cached, and errors now say whether git is missing or just somewhere unsearchable.\n\n**What**\n\nRepeated git invocations now share one cached probe rather than redoing the same two expensive lookups each time: locating the git executable on PATH, and computing a PATH with directories a cloud session can reach stripped out. When git is not found, the error now distinguishes git being absent entirely from git existing only in a directory Claude Code refuses to search.\n\n**Details**\n\n- The cached values are the resolved git executable and the reduced PATH.\n- The \"only in a directory we refuse to search\" case is flagged separately based on the stderr text differing from the plain not-found message.\n\n**Evidence**\n\n`gitExeOnPath`\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}