{"version":"2.1.317","anchor":"chrome-site-passed-in-permission-request-metadata","canonical_anchor":"chrome-site-passed-in-permission-request-metadata","heading":"Permission requests can now name the Chrome site involved","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/chrome-site-passed-in-permission-request-metadata","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Permission requests can now name the Chrome site involved\n\nTool permission requests now also carry the Chrome site involved, when there is one\n\n**What**\n\nWhen Claude Code asks for permission to use a tool, the request already named the agent that asked. It can now also name the website involved, for requests that come from Claude's Chrome browser tools. This is added only when the request has a site attached.\n\n**Why**\n\nPermission requests for browser actions can now be tied to the specific site they concern.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}