tengu_harbor_kite

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

What it is

Presence across releases

A row reading never mined is a release with no archived bundle behind it. Nothing was read out of it, so nothing here says whether the name was in it. A declared type or a default is only ever what that release's own bundle stated.

Gate readings

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.

Changelog entries naming it

1. v2.1.248Kite 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

2. v2.1.248Cross-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

3. v2.1.238Cross-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

4. v2.1.236Asking 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

5. v2.1.236The 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

6. v2.1.236Every session now advertises that it can send idle notices

   Every session now advertises itself as able to send idle notices, with no flag guarding it.

   gate cited by this entry

7. v2.1.232Cross-session message results now describe and pin the target

   Cross-session send results now name the recipient and warn about duplicate or reused names.

   gate cited by this entry

8. v2.1.232@-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

9. v2.1.232@-mentioning another Claude session

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

   gate cited by this entry

10. v2.1.232A /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

11. v2.1.232@-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

12. v2.1.232Hidden cross-session inbox row in the settings dialog

    A cross-session inbox row can appear in settings but stays hidden without a server flag.

    gate cited by this entry

13. v2.1.227Refusing peer messages when cross-session messaging is off is now a distinct case

    Sending messages between your Claude sessions stays off, and refusals now name the kill switch explicitly.

    gate cited by this entry

14. v2.1.224Incoming peer messages get their own transcript rendering

    Messages from another session render as an @sender header with indented body instead of raw tags.

    gate cited by this entry

15. v2.1.224Peer address shown in the session info panel

    The session info panel now shows your peer socket address when cross-session messaging is on.

    gate cited by this entry

16. v2.1.224Remote bridge peers documented as reply-only

    Remote bridge sessions are described as reply-only and unreachable by name.

    gate cited by this entry

17. v2.1.224Cross-session messaging explains why it is unavailable

    Messaging another session now tells you why it failed instead of silently doing nothing.

    gate cited by this entry

18. v2.1.224Remote Control sessions now explain that they are reply-only

    Messaging a Remote Control session now explains it is reply-only until it messages you first.

    gate cited by this entry

19. v2.1.224Cross-session messaging inbox now actually starts at startup

    Startup can now actually open the local socket that lets other sessions message you.

    gate cited by this entry

20. v2.1.224New ListAgents tool for finding other sessions you can message

    A tool that lists other Claude sessions you can message exists but stays off by default.

    gate cited by this entry

21. v2.1.224SendMessage can address other sessions directly and reports delivery timing

    Messages can be addressed to a specific session by socket or id, blocked unless peer messaging is enabled.

    gate cited by this entry

22. v2.1.224Forked sessions are told once that their twin is still running

    A forked session can be told once that its twin is still live and how to reach it.

    gate cited by this entry

23. v2.1.224Forked sessions can be told their original is still running

    A forked session can be told its original is still running and how to message it.

    gate cited by this entry

Documentation pages

None of Anthropic's documentation pages this site has a copy of carries this name.

Names beside it

Every feature flag in the inventory starting tengu_harbor, up to twelve of them.

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.