Cross-session send results now name the recipient and warn about duplicate or reused names.
Richer send-result notes live in the cross-session messaging path, which is gated off by default.
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.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?
Results from sending a message to another session now append a note identifying the recipient, with different wording for cloud and Remote Control targets, a caveat that cloud targets are one-way, and a warning when another session on this machine claims the same name or when a name was previously used by a different session. The resolved target is pinned into app state, and a separate short string is carried for display.
- One warning reads "Note: messaging a new session for the first time under a previously used name (was it restarted?)".
- Gated by
tengu_harbor_kite, which falls back to off, or theCLAUDE_CODE_HARBOR_KITEenvironment variable.
Note: messaging a new session for the first time under a previously used name (was it restarted?)
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.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross