{"version":"2.1.224","anchor":"peer-address-shown-in-the-session-info-panel","canonical_anchor":"peer-address-shown-in-the-session-info-panel","heading":"Peer address shown in the session info panel","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/peer-address-shown-in-the-session-info-panel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Peer address shown in the session info panel\n\nThe session info panel now shows your peer socket address when cross-session messaging is on.\n\n**What**\n\nThe session details list gains a \"Peer address\" row showing the messaging socket as `uds:<path>`. It appears only when cross-session messaging is enabled and `CLAUDE_CODE_MESSAGING_SOCKET` is set; this slot was previously always empty.\n\n**Details**\n\n- Cross-session messaging is gated by `tengu_harbor_kite` or the `CLAUDE_CODE_HARBOR_KITE` environment variable.\n\n**Evidence**\n\n`Peer address`\n\n- Flag `tengu_harbor_kite`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.224; this account: on, anonymous baseline: on, compiled default: off) 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.\n- Area: Cross-Session Messaging\n- Names: `CLAUDE_CODE_MESSAGING_SOCKET`, `CLAUDE_CODE_HARBOR_KITE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}