Bug: Claude in Chrome extension OAuth authorization fails with ERR_BLOCKED_BY_CLIENT and unsupported redirect URI

Resolved 💬 3 comments Opened Mar 25, 2026 by sharanxigiai Closed Mar 29, 2026

Bug Report

Describe the bug:
The Claude in Chrome extension fails to authorize/connect with two distinct errors:

  1. ERR_BLOCKED_BY_CLIENT — Chrome blocks the extension's own options page (chrome-extension://...options.html)
  2. Authorization failed: Redirect URI chrome-extension://.../oauth_callback.html is not supported by client

The extension appears enabled (toggle is blue in Claude Code connectors menu) but never actually establishes a connection to the Claude Code session.

Steps to reproduce:

  1. Install Claude in Chrome extension (Beta)
  2. Open Claude Code and enable the Claude in Chrome connector
  3. Click the extension icon in Chrome toolbar to authorize
  4. Authorization fails with the redirect URI error
  5. Attempting to open the extension options page shows ERR_BLOCKED_BY_CLIENT

Expected behavior:
Extension connects successfully and Claude Code can control the browser.

Environment:

  • macOS
  • Chrome (latest)
  • Claude in Chrome Beta extension
  • Only 2 extensions installed (Claude in Chrome + Google Docs Offline) — no ad blockers

Impact:
Extension is completely unusable. Cannot use any browser automation tools from Claude Code.

🤖 Generated with Claude Code

View original on GitHub ↗

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