[BUG] Claude in Chrome — "blocked by your organization's policy" on all sites (personal Ubuntu machine, no managed policies)

Open 💬 6 comments Opened May 17, 2026 by galejandroz

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?

The Claude in Chrome sidebar shows "Can't access this page — This site is blocked by your organization's policy" on every site, including google.com.

This is a personal machine with no enterprise policies, no MDM, no antivirus, and no managed Chrome profile.

  • chrome://policy — empty
  • chrome://management — not managed

Steps to reproduce:

  1. Open any website (e.g. google.com)
  2. Open the Claude sidebar
  3. Error: "This site is blocked by your organization's policy"

Environment:

  • OS: Ubuntu 24.04.4 LTS (kernel 6.18.5, x86_64)
  • Chrome: 148.0.7778.167 (Official Build) (64-bit)
  • Claude in Chrome extension: v1.0.70
  • Plan: Pro (individual)
  • Chrome profile: personal, no enterprise policies

Related issues: #41034, #50157

What Should Happen?

The Claude sidebar should load normally and be able to interact with any website without being blocked.

<img width="380" height="914" alt="Image" src="https://github.com/user-attachments/assets/21f21a69-32a9-489b-ae57-cff1c8cbfdcf" />

Error Messages/Logs

Can't access this page
This site is blocked by your organization's policy.

Steps to Reproduce

  1. Open any website (e.g. google.com)
  2. Open the Claude in Chrome sidebar
  3. Sidebar shows: "Can't access this page — This site is blocked by your organization's policy"

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.138

Platform

Other

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

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