[BUG] Claude in Chrome extension: hard-blocked on docs.google.com with no way to grant permission

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?

Title: Claude in Chrome extension: hard-blocked on docs.google.com with no way to grant permission

Description:
I'm trying to use Claude (via Claude Code, desktop) with the "Claude in Chrome" browser extension to help build content directly in a Google Form (docs.google.com/forms). All actions on this domain are denied, and there is no way to approve the site.

Steps to reproduce:

1. In Claude Code, ask Claude to navigate to https://forms.new (or any docs.google.com URL) using the Claude in Chrome browser tools.
2. The initial navigate call succeeds and a new Google Form is created.
3. Any follow-up action on that tab (computer screenshot, read_page, further navigate to the same docs.google.com URL) fails immediately with:

• "Permission denied for this action on this domain"
• "Permission denied for reading pages on this domain"
• "Navigation to this domain is not allowed" (on a retry to the same edit URL)

What I checked:

• Opened the Claude extension's own options page (chrome-extension://.../options.html) → "Your approved sites" section says "You have allowed Claude to take all actions (browse, click, type) on these sites." but lists "No sites have been approved yet" — there is no button or field to manually add a site.
• No permission prompt/popup ever appears in Chrome when the action is attempted, so there's nothing to click "Allow" on.
• Fully removed and reinstalled the Claude extension — same errors persisted afterward.

Expected behavior:
Either the extension should show a permission prompt allowing the user to approve docs.google.com, or the "Your approved sites" page should let a user manually add a domain, OR — if Google Workspace domains (docs.google.com, drive.google.com, mail.google.com) are intentionally excluded from generic browser automation as a safety measure — this should be stated clearly to the user/assistant instead of surfacing as a generic, ambiguous "Permission denied" error.

Environment:

• Claude Code on Windows 11
• Claude in Chrome extension, connected to local Chrome browser

What Should Happen?

Title: Claude in Chrome extension: hard-blocked on docs.google.com with no way to grant permission

Description:
I'm trying to use Claude (via Claude Code, desktop) with the "Claude in Chrome" browser extension to help build content directly in a Google Form (docs.google.com/forms). All actions on this domain are denied, and there is no way to approve the site.

Steps to reproduce:

1. In Claude Code, ask Claude to navigate to https://forms.new (or any docs.google.com URL) using the Claude in Chrome browser tools.
2. The initial navigate call succeeds and a new Google Form is created.
3. Any follow-up action on that tab (computer screenshot, read_page, further navigate to the same docs.google.com URL) fails immediately with:

• "Permission denied for this action on this domain"
• "Permission denied for reading pages on this domain"
• "Navigation to this domain is not allowed" (on a retry to the same edit URL)

What I checked:

• Opened the Claude extension's own options page (chrome-extension://.../options.html) → "Your approved sites" section says "You have allowed Claude to take all actions (browse, click, type) on these sites." but lists "No sites have been approved yet" — there is no button or field to manually add a site.
• No permission prompt/popup ever appears in Chrome when the action is attempted, so there's nothing to click "Allow" on.
• Fully removed and reinstalled the Claude extension — same errors persisted afterward.

Expected behavior:
Either the extension should show a permission prompt allowing the user to approve docs.google.com, or the "Your approved sites" page should let a user manually add a domain, OR — if Google Workspace domains (docs.google.com, drive.google.com, mail.google.com) are intentionally excluded from generic browser automation as a safety measure — this should be stated clearly to the user/assistant instead of surfacing as a generic, ambiguous "Permission denied" error.

Environment:

• Claude Code on Windows 11
• Claude in Chrome extension, connected to local Chrome browser

Error Messages/Logs

Steps to Reproduce

Title: Claude in Chrome extension: hard-blocked on docs.google.com with no way to grant permission

Description:
I'm trying to use Claude (via Claude Code, desktop) with the "Claude in Chrome" browser extension to help build content directly in a Google Form (docs.google.com/forms). All actions on this domain are denied, and there is no way to approve the site.

Steps to reproduce:

1. In Claude Code, ask Claude to navigate to https://forms.new (or any docs.google.com URL) using the Claude in Chrome browser tools.
2. The initial navigate call succeeds and a new Google Form is created.
3. Any follow-up action on that tab (computer screenshot, read_page, further navigate to the same docs.google.com URL) fails immediately with:

• "Permission denied for this action on this domain"
• "Permission denied for reading pages on this domain"
• "Navigation to this domain is not allowed" (on a retry to the same edit URL)

What I checked:

• Opened the Claude extension's own options page (chrome-extension://.../options.html) → "Your approved sites" section says "You have allowed Claude to take all actions (browse, click, type) on these sites." but lists "No sites have been approved yet" — there is no button or field to manually add a site.
• No permission prompt/popup ever appears in Chrome when the action is attempted, so there's nothing to click "Allow" on.
• Fully removed and reinstalled the Claude extension — same errors persisted afterward.

Expected behavior:
Either the extension should show a permission prompt allowing the user to approve docs.google.com, or the "Your approved sites" page should let a user manually add a domain, OR — if Google Workspace domains (docs.google.com, drive.google.com, mail.google.com) are intentionally excluded from generic browser automation as a safety measure — this should be stated clearly to the user/assistant instead of surfacing as a generic, ambiguous "Permission denied" error.

Environment:

• Claude Code on Windows 11
• Claude in Chrome extension, connected to local Chrome browser

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

e/g/1/102/23

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_