Claude in Chrome: browser targeting is nondeterministic across Chrome profiles, windows, and devices

Environment

• macOS (Darwin 25.x), two machines (Mac Studio + MacBook), both running Chrome with the Claude in Chrome extension
• 5 Chrome windows across 2 Google profiles on the primary machine (2 windows on a personal account, 3 on a Workspace account)
• Driven from Claude Code sessions via the claude-in-chrome MCP tools, including recurring/scheduled jobs

Problem

Browser targeting is nondeterministic on three axes:

1. Wrong profile/window: tool calls open new tabs / tab groups in a seemingly random Chrome window, hopping between the personal-account and Workspace-account profiles. There is no way to durably say "always use this window/profile."
2. Wrong device: a recurring job running on the Mac Studio intermittently opens tabs on the MacBook's Chrome instead — the extension appears to pick whichever connected browser it likes across devices.
3. No session reuse: consecutive requests in the same session rarely reuse the previously used browser/tab; nearly every request opens new tabs, often in a different window than the last one.

list_connected_browsers shows multiple entries with generic names (e.g. "Browser 2"), so even manual select_browser targeting is guesswork, and the selection does not stick across requests/sessions.

Expected

• A stable, user-visible identity per connected browser (device + profile name)
• Deterministic default: same session keeps using the browser/window it started with
• A way to pin a device+profile as the permanent default for a machine or a session
• Scheduled/recurring jobs never reach across devices unless explicitly told to

Actual

Tabs and tab groups appear in random windows, random profiles, and sometimes on the wrong machine entirely; each request may pick a different target.

Impact

Makes the extension unusable for multi-profile setups (personal vs Workspace) — automation leaks browsing activity across Google accounts and across machines.