Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.277 ·

Multi-store-sync's empty-receipt handling loses its tengu_typed_koala gate and moves inline

Clearing a stale empty store receipt before syncing no longer depends on the tengu_typed_koala flag

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaTeam Memorywhat it touches
KindImprovementsin v2.1.277,
You'll notice

Clearing a stale empty store receipt before syncing no longer depends on the tengu_typed_koala flag

What

Claude Code keeps local "receipts" on disk to track whether a data store has been synced. Previously, clearing out a stale or empty receipt before a sync required a feature flag called tengu_typed_koala to be turned on, in addition to two other conditions. That flag check is now gone: the logic runs unconditionally, and the two other conditions (whether the on-disk receipt is empty, and whether a pull has already happened) have moved into the function that does the actual work.

Why

This behavior no longer depends on a feature flag, so it applies the same way everywhere rather than only when that flag was enabled for a given account.

Read from
Feature flag
tengu_typed_koala On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

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

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

See this entry in the whole of v2.1.277 →