Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

Directory-sync path checks moved onto the storage backend

Path checks for directory sync go through the storage backend, and the mismatch warning wording is shared.

Under the hood Internal Changes
JSON All of v2.1.242
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Directory SyncArea: what it touches
Internal ChangesKind: in v2.1.242,
Internal ChangesSection of the release
What

Checks on paths owned by directory sync now classify a path as real, absent, redirected or not-a-directory through the storage backend when that backend is active, falling back to walking the path with lstat otherwise. The message you see when a session's sync was set up from a different directory now comes from a single shared helper on both paths.

Details
  • Probe failures now have distinct codes, and a classifier for a vanished source produces codes such as batch_dir_vanished and source_unverifiable_parent_link.
  • Whether the backend path or the lstat fallback runs is decided by an internal storage-backend check that is not named in the surrounding code.
Evidence

sync-owned path probe: unexpected answer

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.242 →

Feedback