CLAUDE_CODE_HARBOR_KITE_CLOUD turns on cloud peer access; otherwise a server flag decides and it's off.
Cloud peer access sits behind CLAUDE_CODE_HARBOR_KITE_CLOUD and an account entitlement, with the server-side fallback flag off by default.
tengu_harbor_kite_cloud Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · 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?
CLAUDE_CODE_HARBOR_KITE_CLOUD turns on cloud peer access. It only applies on top of first-party authentication and the allow_remote_sessions entitlement; without the variable the feature falls back to a server-side flag that is off by default. Setting it in .claude/settings.json or settings.local.json is ignored with a warning, since it is registered as blocked at project scope.
- Boolean env var, read after the base harbor-kite gate passes.
- Server fallback is
tengu_harbor_kite_cloud, default off.
CLAUDE_CODE_HARBOR_KITE_CLOUD=1 claudeCLAUDE_CODE_HARBOR_KITE_CLOUD
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