[BUG] Chrome Extension Fails to Inspect site within an existing Tab Group

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?

Claude Chrome Extension reports site blocked by organisation policy, even when allowed in Settings if page is open within an existing Chrome Tab Group.

What Should Happen?

Side panel opens with access to site.

Error Messages/Logs

Workflow stopped
This site is blocked by your organization's policy

Steps to Reproduce

Steps to reproduce: open a site in any existing Chrome tab group, then open the Claude side panel for that tab.
Expected: Claude either moves the tab into its own group, prompts the user, or works without requiring its own group.
Actual: "This site is blocked by your organization's policy" error, with no indication that tab grouping is the cause.
Workaround: remove the tab from its existing group before opening the side panel.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

v1.0.70

Platform

Other

Operating System

macOS

Terminal/Shell

Other

Additional Information

Chrome Extension v1.0.70.

Occurs with any AI model selected.