tengu_harbor_kite_win

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.229, including the newest one read.

Releases whose published page names tengu_harbor_kite_win.

1. v2.1.296 9 Oct 2026
   Administrators can now switch off messaging beyond a user's own agents

   A managed setting, messagingBeyondOwnAgentsDisabled, now turns this feature off and overrides CLAUDE_CODE_HARBOR_KITE

   gate cited by this entry

2. v2.1.248 27 Aug 2026
   Kite network transport now defaults on, including on Windows

   The kite network transport is on by default everywhere, and CLAUDE_CODE_HARBOR_KITE=0 now really turns it off.

   gate cited by this entry, found in this entry's text

3. v2.1.248 27 Aug 2026
   Cross-session peer messaging is on by default

   Sessions can message each other by default now, including on Windows; the cloud variant stays off.

   gate cited by this entry, found in this entry's text

4. v2.1.238 20 Aug 2026
   Cross-session peer identity is now keyed to the account, still off by default

   Session-to-session messaging identity now follows your account, but the whole feature is off by default.

   gate cited by this entry, found in this entry's text

5. v2.1.236 19 Aug 2026
   Asking another local session to ping you when it goes idle, built end to end but not offered to the model

   Your session already honours idle-ping requests from other sessions; only asking for one is gated off.

   gate cited by this entry, found in this entry's text

6. v2.1.236 19 Aug 2026
   The message tool's notify_when_idle parameter and its supporting layer

   Claude can ask another session to ping it when idle, but the parameter is hidden unless the gate is on.

   gate cited by this entry, found in this entry's text

7. v2.1.232 13 Aug 2026
   @-mention completion for other Claude sessions

   You could @-mention your other Claude sessions from the prompt box, but the flag is off by default.

   gate cited by this entry, found in this entry's text

8. v2.1.232 13 Aug 2026
   @-mentioning another Claude session

   Typing @name could message another live Claude session; the feature is off by default.

   gate cited by this entry, found in this entry's text

9. v2.1.232 13 Aug 2026
   A /config row for messages from your other sessions

   A settings row for handling messages from your other sessions exists but is hidden here.

   gate cited by this entry, found in this entry's text

10. v2.1.232 13 Aug 2026
    @-mentions can resolve other sessions, behind a flag

    @-mentions can point at another session instead of a file, but that stage is off here.

    gate cited by this entry, found in this entry's text

11. v2.1.229 12 Aug 2026
    Windows now has its own gate for Harbor cross-session messaging

    Setting CLAUDE_CODE_HARBOR_KITE forces cross-session messaging on, and Windows can now be allowed through.

    gate cited by this entry, found in this entry's text

Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.

One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.

The earliest release whose published evidence quoted tengu_harbor_kite_win was v2.1.229, 12 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.