[BUG] Chrome MCP returns "Navigation to this domain is not allowed" / "Permission denied for this action on this domain" for every domain, persists through reinstall

Resolved 💬 3 comments Opened May 3, 2026 by Fulixintel Closed May 5, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After approving an initial localhost permission prompt mid-session, all subsequent calls to mcp__Claude_in_Chrome__navigate, computer (screenshot, key, type), read_page, javascript_tool return "Navigation to this domain is not allowed" or "Permission denied for this action on this domain". The block applies to every URL, not just the originally denied one (example.com, 127.0.0.1, localhost all fail identically).

What Should Happen?

Tried, did not fix:

Chrome quit + restart
Claude Chrome extension uninstall + reinstall (deviceId changed: 7180ca02-… → adb1d0ba-…)
Claude Code CLI restart
Chrome extension "Site access: On all sites"
chrome://extensions → Reset permissions for the Claude extension
select_browser re-pair, tabs_create_mcp fresh tab
CLI permissions (fine): mcp__Claude_in_Chrome__navigate, …computer, …browser_batch, etc. all explicitly allowed in .claude/settings.local.json.

Hypothesis: A per-domain or global "denied" entry is cached server-side on the Claude account, surviving every client-side reset. There's no surfaced UI to clear it.

deviceId of affected install: adb1d0ba-d2d6-4a13-aa87-b6456a441bd8

Error Messages/Logs

Steps to Reproduce

Tried, did not fix:

Chrome quit + restart
Claude Chrome extension uninstall + reinstall (deviceId changed: 7180ca02-… → adb1d0ba-…)
Claude Code CLI restart
Chrome extension "Site access: On all sites"
chrome://extensions → Reset permissions for the Claude extension
select_browser re-pair, tabs_create_mcp fresh tab
CLI permissions (fine): mcp__Claude_in_Chrome__navigate, …computer, …browser_batch, etc. all explicitly allowed in .claude/settings.local.json.

Hypothesis: A per-domain or global "denied" entry is cached server-side on the Claude account, surviving every client-side reset. There's no surfaced UI to clear it.

deviceId of affected install: adb1d0ba-d2d6-4a13-aa87-b6456a441bd8

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.5354.0 (9a9e3d) 2026-04-29T01:14:34.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗