{"version":"2.1.288","anchor":"chrome-permission-grant-rule-metadata","canonical_anchor":"chrome-permission-grant-rule-metadata","heading":"Chrome tool permission checks record more detail; settings rows can show a notice","tier":"notice","area":"Chrome & Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/chrome-permission-grant-rule-metadata","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Chrome tool permission checks record more detail; settings rows can show a notice\n\nChrome tool permission prompts now carry the client platform, the granting rule and classifier status, and settings rows can show a short notice\n\n**Unclear.** Whether these details are shown to you anywhere is not established.\n\n**What**\n\nWhen Claude uses the Chrome browser tools, Claude Code checks whether each action is allowed. Those checks now carry more information:\n\n- Permission checks for Chrome tools now pass `messageClientPlatform`, the platform the message came from.\n\n- Chrome permission prompts include a `grantRule` (the rule that allowed it) and `classifierUnavailable` in their details.\n\n- The reason given for an allowed domain is now built by a shared helper instead of being written inline.\n\n- Separately, rows in the settings dialog can now show a short `notice` after the pointer symbol in their description.\n\n**Why**\n\nThe permission decision for browser actions now records which rule allowed it and whether the automatic checker was available, which may support a more detailed prompt. Otherwise there is little visible change.\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}