anthropics / anthropics/claude-code

[BUG] **Title:** Claude in Chrome side panel: every tool fails ("Tool X failed in the extension") — `browser_extension` API returns `org_policy: "block"`, `policy_source: "account_disabled"` on a personal account with no org policies (Linux)

Offen
#91,889 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
area:browser-extension area:chrome bug duplicate platform:linux
Vorherrschende Sprache
Python
Sterne
145k
Forks
23.1k
PR-Merge-Kennzahlen
PR-Kennzahlen ausstehend

Beschreibung

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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?

### Summary

Cowork side panel connects and chats normally, but every browser tool (`screenshot`, `tabs_context_mcp`, `get_page_text`, `read_console_messages`) fails instantly with `Tool "" failed in the extension`. The sidepanel bootstrap logs `Connected to parent: claude-in-chrome-sidepanel with 0 tools` and `CURRENT_TAB undefined`. The extension's config call `GET …/browser_extension` returns `org_policy: "block"`, `policy_source: "account_disabled"` for every site tested. The account is a personal org (no Team/Enterprise admin controls), and no Chrome enterprise policies are set. Reproduced identically in Google Chrome (RPM) and Chromium (Flatpak).

### Environment

- OS: openSUSE Tumbleweed (x86_64)
- Browser A: Google Chrome 152.0.7977.75 (official RPM) — reproduced
- Browser B: Chromium 152.0.7977.64 (Flathub `org.chromium.Chromium`) — reproduced
- Extension: Claude in Chrome 1.0.90 (`fcoeoabgfenejglbffodgkkbkcdhcgfn`), Site access: On all sites, Collect errors: on, no errors listed
- Account: personal organization, plan: **Max**, region: Tanzania
- Claude Desktop: not installed. Claude Code CLI (via VS Code Flatpak) works normally.
- `chrome://policy`: `BlockThirdPartyCookies`, `DefaultCookiesSetting`, `ExtensionSettings` all "Not set". Third-party cookies allowed.
- Native messaging: `~/.config/google-chrome/NativeMessagingHosts/` and `~/.config/chromium/NativeMessagingHosts/` both empty (no `com.anthropic.claude_*` manifests).

### Actual

```
Tool "computer" failed in the extension.
Tool "tabs_context_mcp" failed in the extension.
Tool "get_page_text" failed in the extension.
Tool "read_console_messages" failed in the extension.
```

After a few attempts the `claude-in-chrome` MCP server disconnects from the session; a reconnect attempt sits in "pending" ~30 s, then fails.

### Evidence

**sidepanel.html console (Inspect views → sidepanel.html):**

```
[BOOTSTRAP] Connected to parent: claude-in-chrome-sidepanel with 0 tools
[BOOTSTRAP] Received parent event: CURRENT_TAB undefined
Datadog Browser SDK: No storage available for session. We will not send any data.
Framing 'https://a.claude.ai/' violates the following Content Security Policy directive:
"frame-ancestors https://claude.ai https://*.claude.ai https://anthropic.com https://*.anthropic.com https://*.ant.dev". The request has been blocked.
[MCP] [AutoSyncConnectorsToSession] Syncing 3 enabled MCP tool(s) to session cse_…
[LOCAL_SESSION] unknown sdk message type: autocompact_state
```

**`browser_extension` config response (sidepanel Network tab, 200 OK):**

```json
{
"url": "https://claude.ai/",
"domain": "claude.ai",
"category": "category0",
"org_policy": "block",
"policy_source": "account_disabled"
}
```

**Service-worker network log:** only `api.anthropic.com/api/event_logging/v2/batch` (200) and `api.segment.io/v1/batch` (blocked by local DNS filter — analytics only). No websocket to `bridge.claudeusercontent.com` is attempted in either browser.

### Ruled out

- DNS/network: queried the local resolver's exact blocklist config; `claude.ai`, `api.anthropic.com`, `claudeusercontent.com`, `bridge.claudeusercontent.com` all resolve. Only analytics hosts (Segment, Sentry, Datadog, Statsig) are blocked. All 211 requests in the sidepanel Network tab return 200.
- Browser: same result on Google Chrome RPM and Chromium Flatpak.
- Chrome policy / cookies / storage partitioning: nothing set; `#third-party-storage-partitioning` flag no longer exists in 152.
- Native-messaging host conflicts (#54567): no manifests present.
- Extension reinstall, Chrome restart, new conversations, DevTools closed, tab in foreground: no change.

### Related

#59974 (Pro, Ubuntu, "blocked by your organization's policy" on all sites), #51599 (`org_policy: "block"` for all HTTPS), #50157.

### Request

Please confirm what sets `policy_source: "account_disabled"` on a personal account and how it can be cleared, or whether this is plan/rollout gating. If gating, the extension should surface that instead of registering 0 tools and failing every call with a generic "failed in the extension".

### What Should Happen?

### Expected

Screenshot returned.

### Error Messages/Logs

```shell

```

### Steps to Reproduce

### Steps to reproduce

1. Install extension in a fresh Chrome profile, sign in.
2. Open any site (e.g. `https://claude.ai/`), open the Claude side panel, start a new conversation.
3. Ask: "take a screenshot".

### Claude Model

Other

### Is this a regression?

I don't know

### Last Working Version

_No response_

### Claude Code Version

2.1.250 (Claude Code)

### Platform

Anthropic API

### Operating System

Other

### Terminal/Shell

Other

### Additional Information

_No response_

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

The payload names sidepanel.html, the browser_extension config request, and the service-worker network log; inspect those entry points first and compare them with related issues #59974, #51599, and #50157. Done means identifying where account_disabled is set and defining a user-visible outcome for blocked tools, but the issue does not name a repository file or test.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
linux, web-dev
Bereich
api, frontend
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Aktiv
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.