{"version":"2.1.311","anchor":"peer-message-posting-stamps-an-origin-record","canonical_anchor":"peer-message-posting-stamps-an-origin-record","heading":"Messages between sessions now say who sent them","tier":"notice","area":"Peer Messages","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/peer-message-posting-stamps-an-origin-record","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Messages between sessions now say who sent them\n\nA message one Claude Code session posts to another now carries a record of the sender, its name, its mode and its plugin\n\n**What**\n\nClaude Code sessions can post messages to one another, called peer messages. Each posted message now carries an origin record. Before, it had none. The record includes:\n\n- the sender\n\n- the sender's name\n\n- the mode the sender was in\n\n- the plugin involved\n\n- the message body, but only when it is within a size limit and has no file attachments\n\nIn some cases Claude Code leaves the record off.\n\n**Why**\n\nThe session that receives a peer message can now tell which session sent it.\n\n- Area: Peer Messages\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}