{"version":"2.1.293","anchor":"chrome-permission-prompt-reports-why-a-tab-url-could-not-be","canonical_anchor":"chrome-permission-prompt-reports-why-a-tab-url-could-not-be","heading":"Chrome permission denials now record why a tab's address could not be read","tier":"internal","area":"Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/chrome-permission-prompt-reports-why-a-tab-url-could-not-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Chrome permission denials now record why a tab's address could not be read\n\nWhen Claude Code cannot read a Chrome tab's web address and denies the action, it now records the reason and how long the lookup took\n\n**What**\n\nWhen Claude works in Chrome, Claude Code looks up the web address of the tab before deciding on permission. If it cannot get that address, it still denies the action, as before. What changed is the record it keeps of the denial. Before, it only noted that the address could not be found. Now it notes either that the tab is not a web page or the specific reason the lookup failed, along with how long connecting and the lookup took.\n\n**Why**\n\nThe behaviour you see is the same, but denials in the browser are now much easier to diagnose.\n\n- Area: Chrome\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}