Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

New attach-sync safety check for directory sync (git worker), gated by tengu_violin_soundpost

Directory sync gains a pre-attach safety check to verify a checkout can attach cleanly, behind a new gate

Nothing to try yet No documentation found In Development
JSON All of v2.1.277
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Directory SyncArea: what it touches
In DevelopmentKind: in v2.1.277,
In DevelopmentSection of the release

Unclear No reading of the tengu_violin_soundpost gate has been taken, so whether it is active is unknown.

What

The directory-sync git worker now has an attachSyncEnabled check that determines whether attaching to an existing remote or local checkout would succeed cleanly, before doing so. It returns one of several states: "unanswered", "switched_off", "commit_not_held", "other_branch", "lines_up", or "not_in_history". A companion function proactively re-triggers this check while sync is in a "listening" state.

Why

This is meant to catch cases where a directory-sync checkout can't cleanly attach to the expected commit or branch before problems occur, rather than after. This behavior is controlled by a setting called tengu_violin_soundpost.

Read from
Names in the bundletengu_violin_soundpost
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 doubtNo reading of the `tengu_violin_soundpost` gate has been taken, so whether it is active is unknown.
The name it cites is new in this buildNew in this build: tengu_violin_soundpost

See this entry in the whole of v2.1.277 →

Feedback