[BUG] Claude Desktop → Claude in Chrome: navigate fails with "Navigation to this domain is not allowed" on all domains, no permission prompt shown[BUG]

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Sep 4, 2026 · closed Sep 7, 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?

Every browser navigate action issued from Claude Desktop through the Claude in Chrome integration fails immediately with "Navigation to this domain is not allowed" — for every domain tested, including neutral ones like example.com and google.com. No permission prompt/dialog ever appears in Chrome for the user to approve the domain. Other interactive actions (keyboard input, clicking) fail the same way with "Permission denied for this action on this domain."

What Should Happen?

Navigation should either succeed, or Chrome should show a permission prompt asking the user to approve the domain before Claude Desktop acts on it.

Error Messages/Logs

Navigation to this domain is not allowed
Permission denied for this action on this domain

Steps to Reproduce

  1. Install/connect the Claude in Chrome extension, signed in with the same account as Claude Desktop.
  2. In Claude Desktop, ask Claude to navigate the browser to any URL (e.g. "go to example.com").
  3. Observe: "Navigation to this domain is not allowed" — no popup appears in Chrome.

Note: The same extension works correctly when driven directly from its own side panel inside Chrome (e.g. asking it there to visit facebook.com succeeds immediately, confirmed action taken).
Note: Re-pairing the browser (via the Chrome integration card in Claude Desktop, "Install"/reconnect) produces a fresh device pairing (new deviceId) but does not fix the issue.
Note: Tab management (listing/creating tabs) works fine through the same connection — only interactive actions (navigate, click, type) fail.
Note: Chrome extension's own "Site access" permission is set to "On all sites" (most permissive). No domain-level allow/deny rules exist in any Claude Code settings.json.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude_1.44121.4.0_x64__pzs8sxrjxfjjc

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

This bug is specifically in Claude Desktop (Windows) using the Claude in Chrome extension v1.0.90 integration — not the Claude Code CLI. If this repo isn't the right place for Desktop app bugs, please redirect me to the correct channel.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗