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 ·

Directory-sync state now tracks repository trust and locally-served tools

Cloud session sync and directory-sync change detection now include repositoryTrust and localTools fields

Group of 2 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
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
In DevelopmentKind: in v2.1.277,
In DevelopmentSection of the release

Unclear The gate tengu_violin_bridgepin read off for this site's account and off for the anonymous baseline, with no reading yet taken under this release, so it's unclear whether or how it governs this behavior.

What

When a remote session attaches, the served-tools announcement now feeds a new localTools field, and a new repositoryTrust field is attached to the cloud-session-sync payload when the repository-trust feature is active. The directory-sync journal's change-detection logic was updated to compare both repositoryTrust and localTools (alongside the existing whileClosed field) using a new deep-equality helper, so changes to either are now detected. New status text such as "served by this machine" and "not serving this session" was added to describe trust/sync status to the user.

Why

This lets directory sync correctly notice and react when which tools are served locally or the repository's trust state changes, instead of only tracking whether syncing was paused.

Read from
Names in the bundlerepositoryTrustlocalTools
Feature flag
tengu_violin_bridgepin Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.277: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.277. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_violin_bridgepin, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

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 doubtThe gate `tengu_violin_bridgepin` read off for this site's account and off for the anonymous baseline, with no reading yet taken under this…
The name it cites is new in this buildNew in this build: tengu_violin_bridgepin

See this entry in the whole of v2.1.277 →

Feedback