{"version":"2.1.248","anchor":"cross-session-inbox-carries-the-sender-s-process-start-token","canonical_anchor":"cross-session-inbox-carries-the-sender-s-process-start-token","heading":"Cross-session inbox carries the sender's process start token","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cross-session-inbox-carries-the-sender-s-process-start-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cross-session inbox carries the sender's process start token\n\nMessages from your other sessions now identify the exact process run, not just the pid.\n\n**What**\n\nMessages arriving over the local cross-session socket now record a verified process start value along with the sender's pid, so the origin identifies a specific process run rather than just a pid.\n\n**Details**\n\n- The connection handler resolves the peer token once per connection and reuses the token read during setup when the pid matches, instead of re-reading it per message.\n\n**Evidence**\n\n`verifiedPeerProcStart`\n\n- Area: Cross-Session Messaging\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}