The session info panel now shows your peer socket address when cross-session messaging is on.
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.224: 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.224. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The session details list gains a "Peer address" row showing the messaging socket as uds:<path>. It appears only when cross-session messaging is enabled and CLAUDE_CODE_MESSAGING_SOCKET is set; this slot was previously always empty.
- Cross-session messaging is gated by
tengu_harbor_kiteor theCLAUDE_CODE_HARBOR_KITEenvironment variable.
Peer address
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.227
Refusing peer messages when cross-session messaging is off is now a distinct case
Both mention harbor kite cross
-
v2.1.229
Windows now has its own gate for Harbor cross-session messaging
Both mention harbor kite cross
-
v2.1.232
New environment variable for cloud peer access
Both mention harbor kite cross