{"version":"2.1.232","anchor":"clearer-addressing-rules-and-failure-notes-for-cross-session","canonical_anchor":"clearer-addressing-rules-and-failure-notes-for-cross-session","heading":"Clearer addressing rules and failure notes for cross-session messages","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/clearer-addressing-rules-and-failure-notes-for-cross-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Clearer addressing rules and failure notes for cross-session messages\n\nCross-session messaging now explains when a bare name works and when you need a ref.\n\n**What**\n\nSending a message to another agent or session now explains when a bare name is enough and when it is not: an exact match against a single live agent or session delivers directly, while a typed prefix or an unavailable session list means you must supply a ref.\n\n**Details**\n\n- The agent listing now warns separately when the cloud session list could not be fetched and when the local machine list could not be fetched, so you know which half may be short.\n- The listing states that a cloud session cannot message you back yet.\n- Results carry a separate `display` string, and notes call out same-named siblings.\n- Telemetry gained `exactUnique` and `previouslyPinned` attributes on send attempts.\n\n**Evidence**\n\n`The cloud session list could not be fetched just now, so this list may be missing a cloud session; retry if you meant one.`\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}