{"version":"2.1.321","anchor":"chrome-tool-permission-tab-url-resolution-failures-now-deny","canonical_anchor":"chrome-tool-permission-tab-url-resolution-failures-now-deny","heading":"Claude in Chrome now asks or refuses when it cannot tell which page an action targets","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/chrome-tool-permission-tab-url-resolution-failures-now-deny","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Claude in Chrome now asks or refuses when it cannot tell which page an action targets\n\nIf Claude in Chrome cannot work out a tab's address, it now asks you or refuses with a clear message, depending on why\n\n**What**\n\nClaude in Chrome lets Claude act in your browser. Before an action runs, Claude Code checks whether it is allowed, which depends on the page the action targets. When it cannot work out a tab's address, it now sorts out why, and then either asks you or refuses. A refusal says: \"Couldn't determine which page this action targets. Re-read tabs_context_mcp and try again.\" Before, a missing address went down a general path. When actions are grouped together, any page navigations in the group are now collected as well.\n\n**Why**\n\nFor browser actions that are checked automatically, an unclear target now gets a clear refusal or question instead of a vague prompt.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}