Skip to main content
Chrome integration is in beta and currently works with Google Chrome only. It is not yet supported on Brave, Arc, or other Chromium-based browsers. WSL (Windows Subsystem for Linux) is also not supported.
Claude Code integrates with the Claude in Chrome browser extension to give you browser automation capabilities directly from your terminal. Build in your terminal, then test and debug in your browser without switching contexts.

​
What the integration enables

With Chrome connected, you can chain browser actions with terminal commands in a single workflow. For example: scrape documentation from a website, analyze it, generate code based on what you learned, and commit the result. Key capabilities include:
  • Live debugging: Claude reads console errors and DOM state directly, then fixes the code that caused them
  • Design verification: Build a UI from a Figma mock, then have Claude open it in the browser and verify it matches
  • Web app testing: Test form validation, check for visual regressions, or verify user flows work correctly
  • Authenticated web apps: Interact with Google Docs, Gmail, Notion, or any app you’re logged into without needing API connectors
  • Data extraction: Pull structured information from web pages and save it locally
  • Task automation: Automate repetitive browser tasks like data entry, form filling, or multi-site workflows
  • Session recording: Record browser interactions as GIFs to document or share what happened

​
Prerequisites

Before using Claude Code with Chrome, you need:

​
How the integration works

Claude Code communicates with Chrome through the Claude in Chrome browser extension. The extension uses Chrome’s Native Messaging API to receive commands from Claude Code and execute them in your browser. This architecture lets Claude Code control browser tabs, read page content, and perform actions while you continue working in your terminal. When Claude encounters a login page, CAPTCHA, or other blocker, it pauses and asks you to handle it. You can provide credentials for Claude to enter, or log in manually in the browser. Once you’re past the blocker, tell Claude to continue and it picks up where it left off. Claude opens new tabs for browser tasks rather than taking over existing ones. However, it shares your browser’s login state, so if you’re already signed into a site in Chrome, Claude can access it without re-authenticating.
The Chrome integration requires a visible browser window. When Claude performs browser actions, you’ll see Chrome open and navigate in real time. There’s no headless mode since the integration relies on your actual browser session with its login state.

​
Set up the integration

1

Update Claude Code

Chrome integration requires a recent version of Claude Code. If you installed using the native installer, updates happen automatically. Otherwise, run:
claude update
2

Start Claude Code with Chrome enabled

Launch Claude Code with the --chrome flag:
claude --chrome
3

Verify the connection

Run /chrome to check the connection status and manage settings. If the extension isn’t detected, you’ll see a warning with a link to install it.
You can also enable Chrome integration from within an existing session using the /chrome slash command.

​
Try it out

Once connected, type this into Claude to see the integration in action: 
Go to code.claude.com/docs, click on the search box,
type "hooks", and tell me what results appear
Claude opens the page, clicks into the search field, types the query, and reports the autocomplete results. This shows navigation, clicking, and typing in a single workflow.

​
Example workflows

Claude can navigate pages, click and type, fill forms, scroll, read console logs and network requests, manage tabs, resize windows, and record GIFs. Run /mcp and click into claude-in-chrome to see the full list of available tools. The following examples show common patterns for browser automation.

​
Test a local web application

When developing a web app, ask Claude to verify your changes work correctly: 
I just updated the login form validation. Can you open localhost:3000,
try submitting the form with invalid data, and check if the error
messages appear correctly?
Claude navigates to your local server, interacts with the form, and reports what it observes.

​
Debug with console logs

If your app has issues, Claude can read console output to help diagnose problems: 
Open the dashboard page and check the console for any errors when
the page loads.
Claude reads the console messages and can filter for specific patterns or error types.

​
Automate form filling

Speed up repetitive data entry tasks: 
I have a spreadsheet of customer contacts in contacts.csv. For each row,
go to our CRM at crm.example.com, click "Add Contact", and fill in the
name, email, and phone fields.
Claude reads your local file, navigates the web interface, and enters the data for each record.

​
Draft content in Google Docs

Use Claude to write directly in your documents without API setup: 
Draft a project update based on our recent commits and add it to my
Google Doc at docs.google.com/document/d/abc123
Claude opens the document, clicks into the editor, and types the content. This works with any web app you’re logged into: Gmail, Notion, Sheets, and more.

​
Extract data from web pages

Pull structured information from websites: 
Go to the product listings page and extract the name, price, and
availability for each item. Save the results as a CSV file.
Claude navigates to the page, reads the content, and compiles the data into a structured format.

​
Run multi-site workflows

Coordinate tasks across multiple websites: 
Check my calendar for meetings tomorrow, then for each meeting with
an external attendee, look up their company on LinkedIn and add a
note about what they do.
Claude works across tabs to gather information and complete the workflow.

​
Record a demo GIF

Create shareable recordings of browser interactions: 
Record a GIF showing how to complete the checkout flow, from adding
an item to the cart through to the confirmation page.
Claude records the interaction sequence and saves it as a GIF file.

​
Best practices

When using browser automation, keep these guidelines in mind:
  • Modal dialogs can interrupt the flow: JavaScript alerts, confirms, and prompts block browser events and prevent Claude from receiving commands. If a dialog appears, dismiss it manually and tell Claude to continue.
  • Use fresh tabs: Claude creates new tabs for each session. If a tab becomes unresponsive, ask Claude to create a new one.
  • Filter console output: Console logs can be verbose. When debugging, tell Claude what patterns to look for rather than asking for all console output.

​
Troubleshooting

​
Extension not detected

If Claude Code shows “Chrome extension not detected”:
  1. Verify the Chrome extension (version 1.0.36 or higher) is installed
  2. Verify Claude Code is version 2.0.73 or higher by running claude --version
  3. Check that Chrome is running
  4. Run /chrome and select “Reconnect extension” to re-establish the connection
  5. If the issue persists, restart both Claude Code and Chrome

​
Browser not responding

If Claude’s browser commands stop working:
  1. Check if a modal dialog (alert, confirm, prompt) is blocking the page
  2. Ask Claude to create a new tab and try again
  3. Restart the Chrome extension by disabling and re-enabling it

​
First-time setup

The first time you use the integration, Claude Code installs a native messaging host that allows communication between the CLI and Chrome. If you encounter permission errors, you may need to restart Chrome for the installation to take effect.

​
Enable by default

Chrome integration requires the --chrome flag each time you start Claude Code. To enable it by default, run /chrome and select “Enabled by default”.
Enabling Chrome by default increases context usage since browser tools are always loaded. If you notice increased context consumption, disable this setting and use --chrome only when needed.
Site-level permissions are inherited from the Chrome extension. Manage permissions in the Chrome extension settings to control which sites Claude can browse, click, and type on. Run /chrome to see current permission settings.

​
See also