Claude

Anthropic

2.9 (

278 ratings

)

Extension Tools 700,000 users

18 support issues

For additional help, check out the developer's support site.

Daniel Egan

Jan 13, 2026

Claude in Chrome extension cannot execute screenshots, clicks, or JavaScript—only nav

Problem:
Error Message: Cannot access a chrome-extension:// URL of different extension
Environment:

macOS (Mac)
Google Chrome with Claude in Chrome (Beta) v1.0.39
Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn

Troubleshooting Attempted:

✗ Disabled conflicting extensions (Grammarly, GoFullPage)
✗ Enabled "Allow JavaScript from Apple Events" in Chrome → View → Developer
✗ Granted Screen Recording permission to Chrome in macOS Privacy & Security
✗ Full Chrome restart (multiple times)
✗ Created fresh tabs, tested on multiple sites (Google Docs, example.com)
✗ Dismissed Claude overlay banner on page

What Works:

navigate — ✓
wait — ✓
read_page (DOM structure) — ✓
find — ✓
tabs_context_mcp — ✓

What Fails:

screenshot — ✗
left_click — ✗
javascript_tool — ✗

Root Cause Hypothesis: Chrome's extension security model is blocking cross-extension context access. The Claude extension injects an overlay ("Claude is active in this tab group") that Chrome treats as a separate extension context, preventing the MCP connection from capturing or interacting with page content.

Vladislav Samorodov

Jan 12, 2026

Bug Report: Claude for Chrome Extension v1.0.37 - OAuth Authorization Fails

Summary

OAuth authorization in Claude for Chrome extension v1.0.37 fails silently due to multiple Content Security Policy (CSP) violations and a missing oauth_callback.html file.

Environment

- Extension Version: 1.0.37
- Browser: Google Chrome (macOS)
- Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn

Steps to Reproduce

1. Install Claude for Chrome extension v1.0.37 from Chrome Web Store
2. Click on extension icon to open side panel
3. Click "Sign in" / "Authorize" button
4. OAuth authorization page opens at https://claude.ai/oauth/authorize?...
5. Click "Authorize" button on the OAuth consent page
6. Expected: User is redirected to extension and authorization completes
7. Actual: Nothing happens, authorization fails silently

Root Causes Identified

1. Missing oauth_callback.html: File The OAuth flow uses redirect_uri=chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/oauth_callback.html, but this file does not exist in the extension package. When the OAuth server redirects to chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/oauth_callback.html?code=...&state=..., Chrome returns ERR_FILE_NOT_FOUND.
2. CSP Missing platform.claude.com in connect-src

Ken Settle

Jan 5, 2026

Installed the extension in Chrome, but can't Authorize

After installing the Claude Extension in Chrome, when I click the button to authorize the connection to my account, it doesn't work.

It reports this Uncaught (in promise) Object error every time I press the "Authorize" button.
Here is a copy of the console (with duplicates removed):

installHook.js:1 [Sentry] You cannot use Sentry.init() in a browser extension, see: https://docs.sentry.io/platforms/javascript/best-practices/browser-extensions/
overrideMethod @ installHook.js:1
main.js:1 Object
frame-modern.a3775194.js:1 [Intercom] Launcher is disabled in settings or current page does not match display conditions

Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
remote-object-helper-content.js:27 Uncaught (in promise) Object

Allen Tong

Jan 3, 2026

Vivaldi Browser Support

I tried installing with Vivaldi, but the extension doesn't seem to load properly.

heba ahmed

Dec 30, 2025

no model selector, only Haiku is available!

Despite being a Pro user, I'm limited to using only the Haiku model with no option to select other available models. A model selector would greatly improve the experience and give Pro users access to the full capabilities they're paying for.

Mike Hickey

Dec 26, 2025

Query Wizard Search Interface Has Critical Discoverability and UX Issues

ASRS Database Online - Issue Report
Title: Query Wizard Search Interface Has Critical Discoverability and UX Issues

Environment:
Application: ASRS Database Online (v2.9)
URL: https://akama.arc.nasa.gov/ASRSDBOnline/QueryWizard_Filter.aspx
Platform: All modern browsers (Chrome, Firefox, Safari, Edge)

Severity: HIGH
Issue Summary:
The Query Wizard's "Click Here" buttons for selecting search criteria (particularly for Report Number/ACN searches) open in detached popup windows that are not discoverable or easily accessible to users. This creates a poor user experience and makes the interface appear broken when popups don't open in expected locations.

Detailed Problems:
1. Popup Window Opens in New Window, Not New Tab

Problem: When users click "Click Here" to select Report Numbers (ACNs), a popup window opens in a detached window rather than a new browser tab
Impact: Users may not notice the popup has opened, especially if it appears behind the main window or outside their normal tab area
Evidence: Modern browsers default to tabs; windows are rarely used and are often unexpected behavior

2. No Visual Feedback or Instructions

Problem: The interface states "Make sure your Pop-up Blocker is off" but does not:

Confirm when a popup has successfully opened
Direct users where to look for the popup window
Provide clear instructions that a new window (not tab) will open
Show any loading indicator or status message

3. Navigation Issues

Problem: Once a user closes the popup window, there's no clear way to re-open it without starting the entire search process over
Impact: Accidentally closing the popup requires users to remove the search criterion and re-add it

4. No Modal Dialog Alternative

Problem: Modern web applications use modal dialogs or inline editors instead of detached popups
Impact: The current popup approach feels outdated and is not aligned with current web standards and user expectations

Recommended Solutions:
Short-term (Quick Fix):

Add prominent instructions: "A popup window will open (not a tab). Please check your taskbar or behind other windows if it doesn't appear immediately."
Add visual feedback when the popup opens (e.g., "Popup opened - check your desktop" message)
Add a "Re-open Popup" button in case the window is closed

Medium-term (Better UX):

Replace popup windows with modal dialogs within the same window/tab
Implement inline text inputs for ACN entry (comma-separated list)
Add support for ACN ranges (e.g., "2204650-2230585")
Provide clear status indicators showing which search criteria have been configured

Long-term (Modernization):

Redesign the Query Wizard using modern JavaScript frameworks (React, Vue, Angular)
Implement drag-and-drop search builder interface
Add bulk import functionality (paste CSV/JSON of ACNs)
Create an API endpoint for programmatic searches
Add keyboard shortcuts and accessibility improvements

Additional Observations:

Documentation Mismatch: The help text mentions "popup windows" but modern users expect tabs
No Bulk Search: Users with 50+ specific ACNs must enter them one at a time (very inefficient)
Old Technology Stack: The interface appears to use ASP.NET WebForms with client-side JavaScript postbacks, which is outdated

Steps to Reproduce:

Navigate to https://asrs.arc.nasa.gov/search/database.html
Click "Start Search" to open Query Wizard
In the "Date & Report Number" section, locate the "Report Number" link
Click "Click Here" next to "(ACN) was"
Observe: Popup opens in a separate window, not in a new tab (behavior may not be immediately obvious to users)

Files/Screenshots:
Query Wizard main interface screenshot attached
Popup window behavior documented

Business Impact:
Users cannot efficiently retrieve specific reports by ACN
Workflow is time-consuming for researchers needing multiple specific reports
Discoverability issues lead to user frustration and support requests

Mike Hickey

Dec 26, 2025

Limited Functionality with Chrome Extension-Based PDFs (Adobe Acrobat Plugin)

Feedback: Limited Functionality with Chrome Extension-Based PDFs (Adobe Acrobat Plugin)

Issue Description:
Claude cannot interact with or capture screenshots of PDF files opened through Chrome extensions, specifically when using the Adobe Acrobat plugin. PDFs loaded via the chrome-extension:// protocol are inaccessible to Claude's automation tools.

Specific Example:
When navigating to a PDF URL that is intercepted by the Adobe Acrobat Chrome extension (e.g., chrome-extension://efaidnbmnnnibpcajpcglclefindmkaj/https://akama.arc.nasa.gov/ASRSDBOnline/CodingForm.pdf), Claude cannot:

Take screenshots of the PDF content
Read or extract text from the displayed PDF
Navigate within the PDF viewer
Interact with any controls in the extension interface

Impact:
This limitation prevents Claude from helping users who have the Adobe Acrobat plugin enabled in Chrome, as many PDFs are automatically intercepted and opened through the extension rather than through native browser PDF handling. Users must manually access PDF content instead of having Claude assist with navigation and analysis.

Suggested Solution:
Consider enhancing Claude's capability to interact with content displayed through common browser extensions, particularly PDF viewers, or provide guidance to users about disabling such extensions temporarily when they need Claude to interact with PDF documents.
Environment:

Claude for Chrome Version: 1.0.36
Browser: Google Chrome Version: Version 143.0.7499.170 (Official Build) (arm64)
Extension: Adobe Acrobat (chrome-extension://efaidnbmnnnibpcajpcglclefindmkaj/) Version: 25.12.1.2
Use Case: Assisting with document review and information extraction from web-accessible PDFs

Hoshikawa ERI

Dec 25, 2025

Bug Report: Chrome Crash When Using Claude Extension with Split View

Summary:
Chrome browser crashes 100% of the time when the Claude extension is opened while using Chrome's Split View feature.
Steps to Reproduce:
Enable Chrome's Split View feature (available in recent Chrome versions)
Open a split view with two tabs side by side
Attempt to open/activate the Claude extension
Chrome crashes immediately

Akib Ul Huque

Dec 23, 2025

Pro plan - Only Haiku 4.5 available in Chrome extension

I'm on a Pro plan, but I only have access to Haiku 4.5 in the Chrome extension with no model selector visible. Is model selection available for Pro users, or is it Max-only? If it should be available, how do I access it?

gopi pathuri

Dec 19, 2025

Subject: Unable to switch models in browser extension

I am currently using the Claude browser extension, but I cannot find an option to switch between different models (e.g., Sonnet, Opus, or Haiku). The interface does not seem to provide a model selector or any clear way to change the active model while using the extension. Could you please provide instructions on how to do this or look into whether this is a technical issue?