{"version":"2.1.315","anchor":"chrome-permission-prompt-tab-url-failures-get-specific-reaso","canonical_anchor":"chrome-permission-prompt-tab-url-failures-get-specific-reaso","heading":"Clearer internal reasons when Chrome can't read a tab's address","tier":"internal","area":"Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/chrome-permission-prompt-tab-url-failures-get-specific-reaso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Clearer internal reasons when Chrome can't read a tab's address\n\nWhen a Chrome permission prompt can't read the tab's address, Claude Code now records one of five specific reasons\n\n**What**\n\nWhen Claude Code works in Chrome and asks your permission for an action, it tries to read the address of the tab involved. If it cannot, it now records why:\n\n- the request timed out\n\n- there was no tab group\n\n- the answer was not in the expected JSON format\n\n- the answer was an error\n\n- the request needs approval first\n\nBefore, almost any failure was recorded under one catch-all reason.\n\n**Why**\n\nThis is for diagnosing problems and changes nothing you see.\n\n- Area: Chrome\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}