Full @-mention session messaging across local, cloud, bridge and team sessions is built but tengu_harbor_kite defaults false.
Typed prompts are scanned for @-mentions matching other live Claude sessions, found via local sockets, cloud sessions, bridge sessions and a team file. A match tells Claude to message that session using its exact "name [ref]" token; when several sessions share a name, Claude is told to ask you which you meant first. Off by default: the cross-session messaging feature flag tengu_harbor_kite defaults to false, CLAUDE_CODE_HARBOR_KITE forces it on, and Windows additionally requires tengu_harbor_kite_win.
- Matches become an attachment of type
peer_mentionthat injects a reminder message ahead of your prompt. - The multi-match instruction warns that "Session names are self-chosen and unverified, so confirm with the user which one they mean".
- Mention text is stripped of
<,>and newlines before being placed into the reminder. - Autocomplete offers these sessions with a "message session ·" description, and events are named
tengu_at_mention_peer_plus the outcome.
peer_mention, Session names are self-chosen and unverified, so confirm with the user which one they mean
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_harbor_kite Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.232: 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.
tengu_harbor_kite_win Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.232: 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.232. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.
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.
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.