Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Directory sync needs git 2.32 or newer and warns about more setups

Directory sync now runs git with a cleaned environment, needs git 2.32 or newer, and gives new reasons when it cannot read git

You'll notice Improvements
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release
What

Directory 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".

There are new reasons sync gives when it cannot use git normally:

  • volume_in_reach, about a volume within the area sync covers
  • old_git, when git is older than 2.32
  • a case where your home directory is itself a git checkout

The usage report sent to Anthropic when git is not found on the starting path also records more details.

Why

In 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtHow many setups actually run git through this cleaned, version-checked path is not clear.

See this entry in the whole of v2.1.285 →

Feedback