{"version":"2.1.224","anchor":"bridge-messages-from-peers-can-no-longer-skip-the-approval-g","canonical_anchor":"bridge-messages-from-peers-can-no-longer-skip-the-approval-g","heading":"Bridge messages from peers can no longer skip the approval gate","tier":"notice","area":"Editor Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/bridge-messages-from-peers-can-no-longer-skip-the-approval-g","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Bridge messages from peers can no longer skip the approval gate\n\nText arriving over the editor bridge from peers can no longer run immediately without approval.\n\n**What**\n\nIncoming messages on the repl bridge were always classified as ungated because the classification was hardcoded, so any text arriving could be run immediately as a command. Messages are now classified from their content, platform, origin and receiver grouping, and the run-immediately shortcut is taken only when that classification really is ungated. Peer and coordinator messages go through the normal accept-or-hold policy.\n\n**Evidence**\n\n`[bridge:repl] Ran immediate command without enqueue: `\n\n- Area: Editor Bridge\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}