Allow multiple Claude Desktop Code sessions to use Chrome extension simultaneously

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

Claude Desktop App allows running multiple Code sessions simultaneously (one per project folder). Each session has access to the Chrome extension (Claude in Chrome) tool. However, only ONE session can actively use the Chrome extension at a time. All other sessions get an error: "Chrome extension disconnected."

This is a significant workflow limitation. When working on multiple projects that require browser interaction (e.g., checking deployments, managing domains, testing web apps), users must close or stop one session's Chrome usage before another session can access it.

Each Code session should be able to use the Chrome extension independently — either by sharing access or by each session opening its own browser tab group.

Proposed Solution

Each Code session should get its own Chrome tab group. The Chrome extension already supports tab groups — extend this so multiple sessions can each control their own independent tab group simultaneously.

Possible approach:

1. Each Code session creates/claims its own tab group in Chrome
2. 2. Sessions operate independently within their tab group
3. 3. No conflicts between sessions — each has isolated browser context

This would make multi-project workflows seamless, especially in Claude Desktop App where users naturally run multiple Code sessions side by side.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_