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
HomeReleasesv2.1.223entry #51

Claude Code v2.1.223 ·

Peer messages are admitted through a new loop and abuse guard

Incoming peer messages now pass rate, duplicate and loop checks before queuing, with drops shown to you.

You'll notice No documentation found New Features
JSON All of v2.1.223
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Peer MessagingArea: what it touches
New FeaturesKind: in v2.1.223,
New FeaturesSection of the release
What

Incoming peer messages are checked before they reach the queue, so a runaway relay chain or a flood from one sender is dropped rather than processed.

Details
  • checks are a per-sender token bucket, a duplicate-body window, a self-hop loop detector, a relay-chain length cap, and a cap on queued peer messages
  • built-in defaults: bucketCapacity 30, refillPerSecond 0.5, dedupWindowMs 30000, maxSelfHops 10, maxChainLength 28, maxTrackedSenders 256
  • limits are read from remote config key tengu_harbor_kite_limits and fall back to that built-in defaults object
  • rejections surface to the user as a drop notice and are counted in telemetry
Evidence

message has already passed through this session (a peer messaging loop)

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

Read from
Names in the bundletengu_harbor_kite_limits
Feature flag
tengu_harbor_kite_limits Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.223: not a boolean we can read

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.223. 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 [] for tengu_harbor_kite_limits, 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.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_harbor_kite_limits, 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 →

See this entry in the whole of v2.1.223 →

Feedback