I'm running OpenClaw Gateway as a systemd user service (Linger enabled). I expect browser.open({ profile: "openclaw" }) to launch a standalone Chromium instance independently of any external Chrome extension connection.

Current Behavior:

1. If I start Gateway and try to run browser.open({ profile: "openclaw" }), it fails with Can't reach the OpenClaw browser control service (timed out) or No tab connected.
2. I must manually open Chrome and click the OpenClaw extension (set to ON).
3. ONLY THEN does browser.open({ profile: "openclaw" }) work and launch the built-in browser window.

It seems the Gateway's internal browser controller is tightly coupled to the extension's connection state, even when requesting an isolated/built-in profile.

Steps to Reproduce:

1. Start OpenClaw Gateway (clean state, no Chrome running).
2. Run browser.open({ profile: "openclaw", targetUrl: "https://example.com" }).
3. Result: Error (timeout/no tab).
4. Open Chrome, ensure OpenClaw extension is connected (ON).
5. Retry step 2.
6. Result: Success (built-in browser window appears).

Expected Behavior:
The profile="openclaw" (built-in browser) should be self-contained and launchable by the Gateway service directly, without requiring a pre-existing Chrome extension connection as a "keep-alive" signal.

Environment:

• OpenClaw Version: v2026.2.9
• OS: Linux (Ubuntu/Debian)
• Gateway Mode: Systemd User Service (Linger enabled)
• Browser Control: Chrome Extension Relay + Built-in