{"version":"2.1.232","anchor":"agent-to-agent-messaging-says-when-the-local-agent-list-coul","canonical_anchor":"agent-to-agent-messaging-says-when-the-local-agent-list-coul","heading":"Agent-to-agent messaging says when the local agent list could not be read","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/agent-to-agent-messaging-says-when-the-local-agent-list-coul","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Agent-to-agent messaging says when the local agent list could not be read\n\nA failed local agent lookup is now reported as a failure, not as \"no such agent\".\n\n**What**\n\nSending a message to another agent already distinguished the cloud directory and the bridge being unreachable. A third case, the local agent registry failing to answer, is now tracked and shown in the \"not sent\" line, so a lookup failure is no longer reported as if no such agent existed.\n\n**Details**\n\n- The new flag is `localUnavailable`, carried through routing, suggestion suppression and the message shown to you.\n- Listing peers similarly gained a `cloudListFailed` flag.\n\n**Evidence**\n\n`localUnavailable`\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}