Multi-Session Support for Claude in Chrome (Tab Group Isolation)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When running multiple Claude Code instances (a "swarm"), they all share the same Claude in Chrome browser session. This causes:

• Tab conflicts: One Claude instance navigates away from another's work
• Screenshot capturing wrong tabs: Screenshots grab the wrong content
• Actions interfering with each other: Commands from one session affect another's tabs

Real-world use case: I run a business with multiple specialized Claude agents working in parallel:

• Work Claude → Shopify Admin, inventory, orders
• Social Claude → Buffer, Instagram, TikTok
• Support Claude → Email, customer service
• Research Claude → Web research, competitor analysis

All need browser access. Currently they fight for the same tabs, causing constant conflicts and requiring manual intervention.

Current workaround: Use Chrome DevTools MCP with separate --user-data-dir profiles. But this:

• Requires manual Chrome launches with special flags
• Loses the seamless "same session as user" benefit (cookies, authentication, etc.)
• More complex setup that defeats the elegance of Claude in Chrome

Why Claude in Chrome is special: It uses the REAL browser session - same cookies, same authentication, no bot detection issues. This is a major unlock that shouldn't be fragmented across different MCP tools.

Proposed Solution

Add session isolation to Claude in Chrome. Here are three potential approaches:

Option A: Tab Group Isolation (Recommended)

• Each Claude Code instance gets assigned to a specific Chrome tab group
• Tabs within a group are isolated from other groups
• Extension tracks which tabs belong to which session via group ID
• Tab groups are already a native Chrome feature - just needs MCP awareness

Option B: Profile Selection

• Support connecting to different Chrome profiles
• Each Claude instance specifies which profile to use
• Profiles already exist in Chrome - extension would select on connect

Option C: Session Tokens

• Claude in Chrome generates unique session tokens per connection
• Each Claude Code instance uses its own token
• Extension routes commands to correct tabs based on token

Technical notes:

• Claude in Chrome uses Chrome's Native Messaging API
• Tab groups are native Chrome - minimal extension changes needed
• Could be as simple as adding --tab-group or --session-id parameter

Expected behavior:

# Terminal 1 - Work Claude
claude --tab-group work

# Terminal 2 - Social Claude  
claude --tab-group social

# Each instance operates on its own isolated set of tabs

This would be a killer feature for anyone running Claude at scale!

Alternative Solutions

Current workaround: Chrome DevTools MCP with separate --user-data-dir profiles and different debugging ports (9222, 9223, etc).

Problems with workaround:

• Requires launching Chrome manually with --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-profile-1
• Loses the seamless authenticated session (logged into sites, cookies, etc.)
• Need to re-authenticate on every site in each profile
• More complex setup - defeats Claude in Chrome's simplicity

Other tools: Browser MCP also exists but has similar isolation issues and lacks Claude in Chrome's native messaging elegance.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Real scenario from today:

1. I run a sports card business with multiple Claude Code instances for different tasks
2. Work Claude is managing Shopify inventory in one tab group
3. Social Claude needs to schedule Buffer posts in another tab group
4. Research Claude needs to check competitor prices on eBay

What happens now:

• Work Claude navigates to Shopify
• Social Claude takes a screenshot but captures Shopify instead of Buffer
• Research Claude navigates to eBay, disrupting Work Claude's Shopify session
• Constant tab conflicts requiring manual intervention

With this feature:

# Terminal 1
claude --tab-group work  # Only sees/controls work tabs

# Terminal 2  
claude --tab-group social  # Only sees/controls social tabs

Each instance operates independently without conflicts. Massive productivity unlock!

Additional Context

_No response_

Chrome Extension → Native Messaging → chrome-native-host.bat
                                            ↓
                    Named Pipe: \.\pipe\claude-mcp-browser-bridge-{username}
                                            ↓
                    Claude Code session (only ONE can listen)

\.\pipe\claude-mcp-browser-bridge-{username}-{session_id}