What
Sync now resolves git from the absolute directories on the PATH as it was when Claude Code launched, so a later change to PATH cannot make sync run a different git. If git is not found there, sync logs once, records a new telemetry event, and substitutes a deliberately nonexistent path so every sync git call fails rather than running something unexpected.
Details
- Message: "[dirSync] git is not on the absolute entries of the PATH this process was started with; no sync git runs".
- Sentinel path:
/nonexistent/git-not-on-the-PATH-this-process-was-started-with. Every sync git spawn goes through this resolver. - Sync git calls are also hardened: protocols disabled, no lazy fetch, no terminal prompt, explicit bare-repo safety, no submodule recursion.
- The global and system git config passthrough now reads the captured startup environment rather than the live one, and always clears
GIT_CONFIG. - No flag; live wherever directory sync runs.
Evidence
/nonexistent/git-not-on-the-PATH-this-process-was-started-with, tengu_dir_sync_git_not_on_start_path
Strings lifted out of the shipped bundle, so the claim above can be checked against them.