How to Use Claude in Chrome | Beta Limitations and Workarounds Explained

What Is Claude in Chrome — Priority Over Computer Use

Claude in Chrome is an integration that allows Claude Code to directly control Chrome or Edge through the official Claude in Chrome browser extension provided by Anthropic on the Chrome Web Store (Source: Using Claude Code in Chrome (Beta)).

Claude opens a new tab for browser tasks and performs actions on sites where the user is already logged in. When it encounters a CAPTCHA or login screen, it pauses and requests manual input, so automation is not designed to run uncontrolled.

Priority Over Computer Use

The priority order for Claude Code interacting with external services is: MCP connector → Bash → Claude in Chrome → Computer Use. For browser tasks, Claude in Chrome takes priority over Computer Use (Source: Using the Computer from the CLI with Claude).

The Claude in Chrome tier overrides Computer Use's "browser is view-only" restriction, enabling clicks, input, and scrolling via the Chrome extension. The reason Computer Use deliberately limits browser access to view-only is to avoid accidentally pressing a payment button on a phishing site or similar. With Claude in Chrome, the Chrome extension's site permission management serves as the alternative safety mechanism.

Comparison with Computer Use

In short, for any web-based task, Claude in Chrome is always the first choice, and its broad applicability is clear since it works on Linux and Windows environments as well.

Four Requirements — Chrome/Edge / Extension v1.0.36+ / Code v2.0.73+ / Direct Anthropic

Unlike other Claude Code features, Claude in Chrome has strict usage requirements. All four must be met for the extension and CLI to establish communication (Source: Using Claude Code in Chrome (Beta)).

There is an additional constraint: WSL (Windows Subsystem for Linux) is not supported. If a Windows user launches Claude Code from WSL rather than a native Windows environment, the Native Messaging path cannot be established and the Chrome extension cannot be reached. If you regularly use WSL, switch to native Windows Claude Code or set up a configuration using Chrome on Linux.

Why Brave and Arc Don't Work

Brave and Arc are both Chromium-based and can install Chrome extensions, but their Native Messaging Host configuration search paths differ from Chrome and Edge, so communication between the extension and CLI cannot be established. Anthropic officially states: "Brave, Arc, and other Chromium-based browsers are not yet supported," without ruling out future support.

Until then, developers who use Brave or Arc as their everyday browser will need to open Chrome or Edge only when using Claude in Chrome.

Why Bedrock / Vertex / Foundry Routes Don't Work

For organizations that access Claude via a third-party provider, the Claude in Chrome feature flag is not applied to their account, so the Chrome integration will not launch. Even if an enterprise primarily uses Bedrock, a separate claude.ai account (personal Pro / Max plan) will be needed just for Claude in Chrome.

This is the same limitation as Computer Use and Routines — the latest research preview features are only unlocked under a direct Anthropic plan.

5-Minute Setup — Launch with --chrome Flag or /chrome

Once the requirements are met, setup is completed in two steps (Source: Using Claude Code in Chrome (Beta)).

# Step 1: Install the extension from the Chrome Web Store
# https://chromewebstore.google.com/detail/claude/fcoeoabgfenejglbffodgkkbkcdhcgfn

# Step 2: Launch Claude Code in Chrome mode
$ claude --chrome
# Or run /chrome from within an existing session

# Confirm connection
$ claude
> /chrome
# Choose "Enabled by default" to avoid passing --chrome every time

When you first enable Chrome integration, Claude Code installs the Native Messaging Host configuration file in the following location. Chrome reads this file at startup, so if "Extension not detected" appears on the first attempt, restart Chrome to pick up the new configuration.

After setup, you can request web tasks in natural language.

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

Trade-offs of "Enabled by Default"

Enabling "Enabled by default" via /chrome means you no longer need to pass --chrome every session, which is convenient, but since browser tools are always loaded, context consumption increases. If you feel context is being used up too quickly, disable this setting and revert to launching with --chrome only when needed.

In the VS Code extension, if the Chrome extension is installed, Chrome is always available with no additional flags required. Note that this behavior differs from the CLI, so be mindful when using both.

Managing Site Permissions

The sites that Claude can browse, click, and type on are inherited from the Chrome extension's site-level permissions. Open the extension details at chrome://extensions and use the "Site access" setting to restrict permitted sites. By default, all sites are accessible, but for sensitive business sites (banks, internal SaaS, etc.), it is safer to use an allowlist approach.

If "Browser extension is not connected" appears during a session, run /chrome and select Reconnect extension. This is the typical recovery procedure when the Service Worker has stopped after a long idle period.

7 Things You Can Do — Live Debugging / E2E Testing / Data Extraction / GIF Recording

Claude in Chrome can chain browser actions and coding tasks within a single workflow. The official documentation outlines seven representative use cases. It is particularly powerful for areas where API connectors are not available, since tasks can be performed via the Web UI (Source: Using Claude Code in Chrome (Beta)).

These are especially powerful for services that "exist on the web but have no API" or "have an API but no MCP connector set up yet" — such as writing directly to Google Docs without an API key, handling manual CRM data entry, or batch-updating Notion pages. You can delegate tasks that humans have been doing through the GUI just as they are.

Notes on Console Debugging

Retrieving console logs is useful, but for large-scale apps with heavy logging, it can consume Claude's context quickly. Rather than vaguely asking to "check all console output," it is more efficient to give narrowed instructions such as "look for a specific error pattern" or "report only errors that appear after login."

For local server development, direct navigation to localhost:3000 also works without issues, so it integrates naturally into frontend development workflows.

Troubleshooting — 4 Common Errors

The four most frequently encountered errors when using Claude in Chrome are listed below, and the official documentation provides fix procedures for all of them (Source: Using Claude Code in Chrome (Beta)).

The phenomenon of losing connection during long sessions is due to Chrome extension Service Worker specifications and is not a bug on Anthropic's side. If you have not used browser tools for more than an hour, it is safe to preemptively reconnect via /chrome.

On Windows specifically, a "named pipe conflict (EADDRINUSE)" error can occur when another Claude Code session is using the same pipe. Close other sessions using Chrome and then restart.

Summary — When to Choose Claude in Chrome

Claude in Chrome is a fast integration that takes priority over Computer Use for all browser tasks, and it is the first choice for seven use cases: live debugging of web apps, E2E testing, data extraction, operating authenticated services, and GIF recording. It supports all OSes — Linux, Windows, and macOS — so it also avoids the macOS-only limitation of Computer Use.

The pre-use checklist has four items:

• Use Google Chrome or Microsoft Edge (Brave and Arc are not supported)
• Claude in Chrome extension v1.0.36 or later installed
• Running Claude Code v2.0.73 or later
• Authenticated with a direct Anthropic plan (Pro / Max / Team / Enterprise) — Bedrock / Vertex / Foundry routes are not supported

Setup is complete once you install the extension from the Chrome Web Store and launch with claude --chrome. Choosing "Enabled by default" via /chrome removes the need for the flag, but since context consumption increases, consider the option of launching only when needed.

Since this is a beta version, the API format and supported browsers may change in the future. Check Using Claude Code in Chrome for the latest specifications.

Sources (Primary Information)

• Using Claude Code in Chrome (Claude Code Official Documentation — Beta)
• Using the Computer from the CLI with Claude (Claude Code Official Documentation)
• Browser Automation in VS Code (Claude Code Official Documentation)
• Claude in Chrome Extension (Chrome Web Store)
• Getting Started with Claude in Chrome (Anthropic Support)

Related Articles

• Introduction to Claude Code — 9 Features Anyone Can Use
• Pitfalls of Claude Code Computer Use
• What Is Claude MCP — Full Feature List and 5 Connection Steps
• Claude Code Scheduling — 4 Methods and Their Pitfalls
• Claude Code on Mac — brew + Apple Silicon + Notification Setup