Dropped messages from peers now show a warning naming the sender and reason instead of disappearing.
tengu_harbor_kite_limits Not enough to sayNothing 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's wrong with this entry?
When the peer guard drops an inbound peer message, a warning now appears in the conversation naming the sender and the reason, instead of the message vanishing silently.
- a new React hook subscribes to the peer-guard drop stream and pushes the formatted warning into the transcript
- repeat drops are collapsed into a single warning carrying a suppressed count
- the whole peer-guard subsystem is new in this build, including
[peer-guard]logging and its limits config - limits are tunable via
tengu_harbor_kite_limitsand fall back to built-in defaults
sender exceeded the peer message rate limit
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
Hidden cross-session inbox row in the settings dialog
Both mention harbor kite
-
v2.1.248
Kite network transport now defaults on, including on Windows
Both mention harbor kite
-
v2.1.224
New ListAgents tool for finding other sessions you can message
Both mention harbor kite