{"version":"2.1.221","anchor":"chrome-bridge-gains-roster-change-notifications-retained-too","canonical_anchor":"chrome-bridge-gains-roster-change-notifications-retained-too","heading":"Chrome bridge gains roster change notifications, retained tool args and permission categories","tier":"notice","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/chrome-bridge-gains-roster-change-notifications-retained-too","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Chrome bridge gains roster change notifications, retained tool args and permission categories\n\nThe Chrome bridge now refreshes the extension list on connect or disconnect and keeps pending tool arguments.\n\n**What**\n\nThe bridge context can now tell the UI when the set of connected extensions changes, keeps the arguments of pending tool calls, and accepts a category on incoming permission requests.\n\n**Details**\n\n- New `onPeerRosterChanged` callback fires on pair, peer connect, peer disconnect and teardown, so the extension list can be refreshed.\n- Pending tool calls now retain their `args` instead of discarding them.\n- Permission requests carry a `category` validated against `^category[0-9a-z_]{1,32}$`; a value that does not match is dropped rather than passed through.\n\n**Evidence**\n\n`onPeerRosterChanged`\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}