Setting CLAUDE_CODE_HARBOR_KITE forces cross-session messaging on, and Windows can now be allowed through.
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.229: 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.229. 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 check for Harbor cross-session messaging was rewritten. Setting CLAUDE_CODE_HARBOR_KITE now forces it on regardless of platform. Windows, which previously always returned false, is allowed through when the separate tengu_harbor_kite_win gate is on. The general gate is consulted last. Both gates fall back to off in this build, so unless the environment variable is set, whether it runs is decided by remote config.
tengu_harbor_kite_win
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