Multiple claude --chrome sessions compete for the same browser

[wesnishio]

Problem

Running multiple claude --chrome instances from separate terminals causes them to compete for the same Chrome extension connection. The extension crashes or sessions interfere with each other (tabs get navigated away, forms lose data, etc.).

Current behavior

• All claude --chrome CLI sessions share one native messaging host connection
• Sessions fight over tabs and windows
• Chrome extension dies under concurrent load

Expected behavior

Each claude --chrome session should get its own isolated Chrome window and tab group, similar to how scheduled tasks in the desktop app already work (unique session IDs, separate windows via chrome.windows.create, tab group isolation via chrome.tabGroups).

Suggestion

• Auto-assign a unique session ID per CLI instance
• Route each session to its own Chrome window
• Or add a --chrome-session <id> flag for explicit isolation

Environment

• macOS 15.6.1 (Apple M2 Pro, 32GB)
• Chrome extension v1.0.64
• Running 3-7 concurrent claude --chrome sessions for outreach/fundraising workflows

[github-actions]

Found 3 possible duplicate issues:

1. Multi-Session Support for Claude in Chrome (Tab Group Isolation) #15193
2. [FEATURE] Support targeting specific Chrome instances/profiles for Claude in Chrome integration #15125
3. [SECURITY] Cross-machine data leak via Claude in Chrome MCP — session isolation broken #29814

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #15193.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.