openclaw - 💡(How to fix) Fix [Bug] Every agent shares one Chrome instance — no browser isolation [1 participants]

Bug Description

All OpenClaw agents share a single Chrome instance when using the browser tool, with no isolation between agents. This creates two related problems:

1. No per-agent browser process

When multiple agents (e.g., Silas, Hector, Ben, Tony) use the browser tool simultaneously, they all connect to the same Chrome process. This means:

• Agent A's tabs are visible to Agent B
• Browser state (cookies, sessions, localStorage) is shared
• No concept of "my tabs" vs "your tabs"

2. Shared MCP tool can't handle concurrent requests

The chrome-devtools-mcp tool runs as a single system-level process. When two agents issue browser commands simultaneously, requests can interfere — tab selection races, orphaned tabs, or silent failures.

Expected Behavior

Each agent should get its own fully isolated Chrome instance:

• Agent A → Chrome on port 18801, dedicated user profile
• Agent B → Chrome on port 18802, dedicated user profile
• ...

This ensures:

• Complete browser state isolation
• No cross-agent tab visibility
• Safe concurrent usage
• Clean per-agent browser lifecycle

Workaround

None — this is a fundamental architectural gap for multi-agent deployments.

Environment

• OpenClaw: 2026.4.5
• Chrome: 146.0.7680.177 (headless)
• Chrome-devtools-mcp: 0.21.0
• OS: Linux (Ubuntu)

Related Issues

This is related to but separate from the attachOnly: true mode failing when Chrome wasn't started with remote debugging flags.