Typing @name could message another live Claude session; the feature is off by default.
Full @-mention session messaging across local, cloud, bridge and team sessions is built but tengu_harbor_kite defaults false.
tengu_harbor_kite On for this account, and not off by defaultThe 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.232: 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.
tengu_harbor_kite_win On for this account, and not off by defaultThe 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.232: 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.232. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
New ListAgents tool for finding other sessions you can message
Both mention harbor kite cross
-
v2.1.224
SendMessage can address other sessions directly and reports delivery timing
Both mention harbor kite cross
-
v2.1.224
Forked sessions are told once that their twin is still running
Both mention harbor kite cross