{"version":"2.1.225","anchor":"self-sent-peer-message-detection-ignores-pid-1","canonical_anchor":"self-sent-peer-message-detection-ignores-pid-1","heading":"Self-sent peer message detection ignores PID 1","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/self-sent-peer-message-detection-ignores-pid-1","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Self-sent peer message detection ignores PID 1\n\nInbound peer messages are no longer mistaken for your own when running inside a container.\n\n**What**\n\nInbound peer messages are no longer misattributed to this process when the session runs as PID 1, which is common inside containers.\n\n**Details**\n\n- the self-sent check now takes the pid as a parameter rather than reading it implicitly\n- returns false outright when that pid is 1, so no false `selfSent` match\n- pairs with the ancestor-walk change above\n\n**Evidence**\n\n`selfSent`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}