{"version":"2.1.267","anchor":"peer-session-send-error-now-suggests-the-sessions-new-name","canonical_anchor":"peer-session-send-error-now-suggests-the-sessions-new-name","heading":"Peer-session send error now suggests the session's new name if it was renamed","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/peer-session-send-error-now-suggests-the-sessions-new-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Peer-session send error now suggests the session's new name if it was renamed\n\nSending a message to a renamed peer session now suggests its new name in the error\n\n**What**\n\nWhen Claude Code tries to send a message to another peer or agent session by name and can't find that name, the error message now checks whether that session was renamed, and if so, tells you its current name.\n\n**Why**\n\nThis makes it easier to recover from a \"session not found\" error caused by a rename, since the message now points directly to the name to use instead.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}