{"version":"2.1.318","anchor":"peer-message-body-schema-accepts-claude-desktop-declared-bod","canonical_anchor":"peer-message-body-schema-accepts-claude-desktop-declared-bod","heading":"Messages between sessions include their decoded body in more cases","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/peer-message-body-schema-accepts-claude-desktop-declared-bod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Messages between sessions include their decoded body in more cases\n\nThe SDK's decoded `body` field on peer messages is now also present when Claude Desktop declares it and the text matches\n\n**What**\n\nPeer messages are messages passed between Claude Code sessions or agents. In the SDK, the kit for running Claude Code from your own programs, they can carry a decoded `body` field. It used to be present only when the turn was exactly one message wrapped by Claude Code, or a message from an agent in the same process. It is now also present when Claude Desktop declares the body and the message text holds exactly the same bytes.\n\n**Why**\n\nPrograms reading these messages get the decoded body more often, including for messages from Claude Desktop.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}