{"version":"2.1.223","anchor":"dropped-peer-messages-now-surface-as-warnings-in-the-transcr","canonical_anchor":"dropped-peer-messages-now-surface-as-warnings-in-the-transcr","heading":"Dropped peer messages now surface as warnings in the transcript","tier":"notice","area":"Peer Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/dropped-peer-messages-now-surface-as-warnings-in-the-transcr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Dropped peer messages now surface as warnings in the transcript\n\nDropped messages from peers now show a warning naming the sender and reason instead of disappearing.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- a new React hook subscribes to the peer-guard drop stream and pushes the formatted warning into the transcript\n- repeat drops are collapsed into a single warning carrying a suppressed count\n- the whole peer-guard subsystem is new in this build, including `[peer-guard]` logging and its limits config\n- limits are tunable via `tengu_harbor_kite_limits` and fall back to built-in defaults\n\n**Evidence**\n\n`sender exceeded the peer message rate limit`\n\n- Flag `tengu_harbor_kite_limits`: Not enough to say (read for one account on one subscription tier against v2.1.223; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Peer Messaging\n- Names: `tengu_harbor_kite_limits`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}