Why does the Claude Chrome extension show a gray icon on some tabs?

A gray icon usually means the extension cannot run on that page. This happens on Chrome system pages (like chrome://extensions), the Chrome Web Store, and any site that blocks extension scripts through its content security policy. The extension can only operate on pages where Chrome allows it to inject scripts.

The extension was working and stopped after a Chrome update. What should I do?

Restart Chrome fully rather than just closing tabs. Go to Help > About Google Chrome to check for any pending updates, install them, and restart again. If the extension is still broken, disable and re-enable it in chrome://extensions, or remove and reinstall it from the Chrome Web Store.

Can I use the Claude extension in a work-managed Chrome browser?

That depends on your organization's Chrome management policies. Managed browsers may block extensions that are not on an approved list. Check with your IT department if the extension cannot be installed or is automatically removed after installation.

Does the Claude extension send my browsing data to Anthropic?

The extension interacts with pages you explicitly ask it to act on. For accurate details about what data it sends and how it is handled, read the extension's permissions page and Anthropic's privacy policy before installing it.

The extension installed but I see no icon in the toolbar. Where did it go?

Chrome hides some extension icons behind the puzzle-piece icon in the toolbar. Click the puzzle-piece icon and pin the Claude extension to make its icon visible in the main toolbar at all times.

Claude Chrome Extension Not Working? Checks and Fixes

If the Claude Chrome extension has stopped working, a small set of common causes covers most cases. Here is how to check installation, sign-in, site permissions, and stalled page actions.

July 10, 2026Updated October 21, 20265 min read

When the Claude Chrome extension stops working, the fix is usually one of four things: the extension is disabled or needs updating, you are not signed in, the current site has blocked the extension's scripts, or a page action stalled without an error message. Tools like fenbs can hold the task brief and checkpoint for a browser job, so if a session is interrupted you can pick it up cleanly rather than reconstructing what you were doing.

Check that the extension is installed and enabled

Open chrome://extensions in a new tab and look for the Claude extension in the list. If it is there but the toggle is off, turn it on. If it is not in the list, the extension may have been removed; reinstall it from the Chrome Web Store. After reinstalling, close and reopen any tabs where you want to use it.

Extensions sometimes stop working after a Chrome update if the browser restarts without reloading all extensions. A full Chrome restart, not just closing and reopening a tab, usually resolves this. Open the Chrome menu, go to Help > About Google Chrome to check for pending updates, and restart after any update completes.

Sign-in and session issues

The Claude extension requires an active Claude.ai session. Open claude.ai directly and confirm you are signed in. If you see the sign-in page, log in and then try the extension again. If Claude.ai shows your account but the extension still shows a sign-in prompt, try signing out of Claude.ai and signing back in, then reload the page where you want to use the extension.

Browser cookie blockers or privacy extensions can interfere with the session. If you use an ad blocker or a privacy tool, temporarily disable it on Claude.ai and see whether the sign-in state persists. If it does, add Claude.ai to the tool's allowlist.

Site permissions and blocked scripts

Some websites use content security policies that block extension scripts from running. When you click the Claude extension on a protected page and nothing happens, this is often the cause. Check whether the extension icon in the toolbar appears grayed out or shows a warning badge on that specific tab. Sites that apply strict content security policies include most banking sites, some enterprise tools, and many internal company portals.

You can also check whether the extension has the site permissions it needs. Click the puzzle-piece icon in the Chrome toolbar, find the Claude extension, and open its permissions settings. Confirm it is allowed to run on the site you are working on. If the permission is set to "Click to allow," you will need to grant it on each visit.

Extension conflicts

Other browser extensions can conflict with the Claude extension, particularly those that modify page content, inject scripts, or intercept network requests. To test whether a conflict is the cause, open a new Chrome window in incognito mode with extensions disabled (except Claude), navigate to the same page, and see whether the extension works. If it does, re-enable your other extensions one at a time to find the conflict.

If you are also running Claude Code or using Claude in other environments, see Claude Code not working and Claude Desktop MCP not working for issues specific to those contexts, since they have different causes from browser extension problems.

When a page action stalls mid-task

Sometimes the extension starts a page action and appears to hang without completing or showing an error. This happens most often on pages with dynamic content that changes while the extension is working. Try refreshing the page and starting the task again. If the page requires a login and your session has timed out in another tab, re-authenticate and retry.

If the extension consistently fails on a specific page or type of content, check whether the issue has been reported in Anthropic's community forums. Provide the URL pattern and the behavior you see when reporting. For general Claude availability issues, check claude.ai/status (opens in a new tab) for any active incidents.

How fenbs helps

Keep your browser task brief safe across interrupted sessions

When a browser session is interrupted, the context for what you were doing often lives only in the tab. fenbs keeps the job brief, checkpoint, and any confirmed decisions from a browser session in a project record that survives a restart. Connect a supported AI assistant from Integrations, save where you left off, and the next session starts from the current state rather than guessing.

Create a free account

Free for one person · No credit card · Works with Claude, ChatGPT, Cursor and more

How to do this with fenbs

Create a free account and add a project for the browser-based work you are doing.
Before starting a long browser task, write the task brief and the steps you plan to take as a task in To Do with a clear plan.
After each meaningful checkpoint, update the task with what you completed and what remains. This takes thirty seconds and means a crash or interruption does not cost you the whole session.
If the extension fails and you need to restart, open the task in fenbs and read Where we left off before restarting the job.
Connect Claude or another supported assistant from Integrations so it can read the task context at the start of the next browser session.

For using Claude directly in the browser without an extension, see Claude in Chrome. For problems specific to Claude's MCP connection, see Claude Code MCP not working. For issues with CLAUDE.md configuration files, see claude.md not working.