{"version":"2.1.234","anchor":"peer-messages-can-declare-the-sender-s-permission-class","canonical_anchor":"peer-messages-can-declare-the-sender-s-permission-class","heading":"Peer messages can declare the sender's permission class","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/peer-messages-can-declare-the-sender-s-permission-class","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Peer messages can declare the sender's permission class\n\nMessages from other sessions now say whether the sender was skipping permission prompts.\n\n**What**\n\nA message injected between sessions can now carry an optional `fromMode` of `\"bypass\"` or `\"prompting\"`, saying whether the sender was running tools without asking. A message from the same class can be delivered immediately; a cross-class or undeclared sender is held when the recipient runs tools without asking.\n\n**Details**\n\n- The field is only honoured from the injecting host on local stdin, so a remote peer cannot claim a class for itself.\n\n**Evidence**\n\n`fromMode`\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}