[DOCS] Getting-started Chrome example uses code.claude.com, which is blocked by the extension

Documentation Type

Other

Documentation Location

https://code.claude.com/docs/en/chrome

Section/Topic

"Ask Claude to use the browser"

Current Documentation

> "Go to code.claude.com/docs, click on the search box, type 'hooks',
> and tell me what results appear"

What's Wrong or Missing?

## Description

The getting-started example at https://code.claude.com/docs/en/chrome (step 2)
instructs users to ask Claude to interact with code.claude.com/docs:

> "Go to code.claude.com/docs, click on the search box, type 'hooks',
> and tell me what results appear"

However, the extension blocks all interaction with *.claude.com domains. Every
tool call on a code.claude.com tab returns:

> "This site is blocked by your organization's policy."

## Steps to Reproduce

1. Run claude --chrome (or /chrome in an existing session)
2. Follow the getting-started example exactly as written
3. Ask: "Go to code.claude.com/docs, click on the search box, type 'hooks',

and tell me what results appear"

## Expected Behavior

The example works as documented.

## Actual Behavior

Every tool call immediately returns "This site is blocked by your organization's policy."

Suggested Improvement

## Suggested Fix

Replace code.claude.com/docs in the example with a publicly accessible
third-party site so new users can successfully follow the getting-started guide.

Impact

High - Prevents users from using a feature

Additional Context

## Investigation

To rule out system-level blocking:

• chrome://policy shows no policies set (Chrome Policies, Policy

Precedence, and the Claude extension section all show "No policies set")

To identify the source of the block:

• Opened DevTools on the extension's service worker

(chrome://extensions → Claude → Service Worker)

• Captured a HAR file during the failed tool calls
• HAR contained 11 entries, all successful — Segment analytics calls to

api.segment.io returning HTTP 200. No failed or blocked HTTP requests.

• The call stack in the HAR traces back entirely to

PermissionManager-9s959502.js inside the extension

This confirms the error is thrown programmatically inside the extension's
PermissionManager before any network request is made. The block is not
coming from Chrome, the OS, or the network — it is enforced by the
extension itself on *.claude.com domains.

## Environment

• Extension version: 1.0.66
• Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn
• OS: macOS 15 (Darwin 25.3.0)
• Chrome version: 146.0.0.0