{"version":"2.1.224","anchor":"incoming-peer-messages-get-their-own-transcript-rendering","canonical_anchor":"incoming-peer-messages-get-their-own-transcript-rendering","heading":"Incoming peer messages get their own transcript rendering","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/incoming-peer-messages-get-their-own-transcript-rendering","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Incoming peer messages get their own transcript rendering\n\nMessages from another session render as an @sender header with indented body instead of raw tags.\n\n**What**\n\nA message sent from another session is displayed as an \"@ sender\" header with the body indented below, instead of the raw wrapper tag. Only reachable when cross-session messaging is enabled (`tengu_harbor_kite` gate or `CLAUDE_CODE_HARBOR_KITE`).\n\n**Details**\n\n- The renderer strips the `<cross-session-message ...>` wrapper and reads the sender from its `from=` and `from-name=` attributes.\n- Sender addresses are humanised: a `uds:` address becomes the socket file's basename with `.sock` removed, a `bridge:` address becomes \"(untitled)\", and anything unresolved shows as \"peer\".\n\n**Evidence**\n\n`<\/cross-session-message>`\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_HARBOR_KITE`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}