How do I make Claude Code's --chrome integration target a specific Chrome profile or instance?
When several Chrome profiles or windows are open, Claude Code's --chrome integration connects to whichever browser responds first, so it can control the wrong session. Users who keep work and personal profiles separate want a reliable way to choose the browser. The thread lists the feature request and the workarounds people use while waiting for it.
Originally asked on GitHub: https://github.com/anthropics/claude-code/issues/15125
5 answers
The issue was closed as COMPLETED, but the thread does not say which release added profile or instance selection, and no built-in option for choosing a Chrome profile with --chrome is described in the thread.
Workarounds reported in the thread:
-
Use a dedicated Chrome instance with its own user data directory and a remote debugging port, then connect over CDP instead of the --chrome extension. A commenter launched Chrome with
--remote-debugging-port=9222 --user-data-dir=$HOME/.chrome-claude-profile --no-first-run --no-default-browser-check. Each port maps to one Chrome instance, and you log in once per instance. This is the commenter's own setup, not a documented Claude Code option. -
Log out of all other Chrome accounts so that only the account tied to your Claude subscription is active. One commenter reported this worked for them.
-
Install Chrome for Testing, add your preferred profile, turn off extension syncing, and then install the Claude extension. A commenter said this works but they would rather use their regular Chrome.
The issue body also states that Claude in Chrome may connect to a different computer. The thread does not explain this further.
Did this work for you?-
What @yurukusa tried on GitHub (Worked)
Launched a dedicated Chrome with --remote-debugging-port and a separate --user-data-dir for each instance, then connected over CDP to localhost on different ports.
Source: https://github.com/anthropics/claude-code/issues/15125#issuecomment-4138082287 (opens external site)
Did this work for you?What @jerrydeng tried on GitHub (Worked)
Logged out of all other Chrome accounts so that only the account tied to the Claude subscription remains in the browser.
Source: https://github.com/anthropics/claude-code/issues/15125#issuecomment-3879043402 (opens external site)
Did this work for you?What @cellodude05 tried on GitHub (Worked)
Installed Chrome for Testing, added the preferred profile, turned off extension syncing, and then added the Claude extension.
Source: https://github.com/anthropics/claude-code/issues/15125#issuecomment-3902054152 (opens external site)
Did this work for you?What @pablo-brown-rodriguez tried on GitHub (Partly worked)
Kept Claude in Chrome connected to the business profile only and used a FUSE-mounted Google Drive for the personal account instead of browser automation.
Source: https://github.com/anthropics/claude-code/issues/15125#issuecomment-4131183946 (opens external site)
Did this work for you?