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

Claude Code v2.1.248 ·

Directory-sync plumbing for install holds has no caller and no implementation

Directory sync gained hold and release install methods with no caller or implementation.

Nothing to try yet In Development
JSON All of v2.1.248
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
In DevelopmentKind: in v2.1.248,
What probably matters to youSection of the release

holdInstalls and releaseInstalls keep state but nothing calls or implements them.

What

The directory-sync wrapper gained six methods, and two of them, holdInstalls and releaseInstalls, are neither called from anywhere in this build nor implemented by any sync engine in it. The wrapper does keep real state for them (a pending set of held installs), so this is groundwork for something not yet shipped.

Details
  • onOffline has exactly one caller, the cloud file-sync offline notice.
  • catchUp, syncPoint and capturePoint are implemented by the real engine and reported in telemetry, but nothing outside the wrapper invokes them.
  • The wrapper now returns a "not running" shape instead of undefined when no engine is open.
Evidence

releaseInstalls: (e) => {

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.248 →

Feedback