openclaw - 💡(How to fix) Fix [Bug]: Desktop cannot use existing Chrome sessions: EasyClaw Google sign-in fails, and user profile attach fails with spawn npx ENOENT [1 participants]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

On Genspark Claw Desktop, two paths to use existing Chrome sessions both fail: (1) EasyClaw Browser Relay extension Google sign-in returns an error after OAuth callback, (2) built-in user profile attach fails with spawn npx ENOENT because Desktop bundles node but not npm/npx.

Steps to reproduce

Repro 1: EasyClaw extension

1. Install "OpenClaw Browser Relay — EasyClaw" Chrome extension
2. Click extension icon → shows "Not connected" + "Sign in"
3. Click "Sign in" → "Continue with Google"
4. Google OAuth completes → error page on callback

Repro 2: user profile

1. Open Chrome 147, enable remote debugging at chrome://inspect/#remote-debugging
2. Use browser tool with profile="user"
3. Fails with: Chrome MCP existing-session attach failed — Error: spawn npx ENOENT

Expected behavior

OpenClaw should attach to the running Chrome session and expose tabs for agent control, as documented at https://docs.openclaw.ai/tools/browser

Actual behavior

EasyClaw: Google OAuth callback returns error page, extension stays "Not connected", no tabs visible to Gateway.

user profile: spawn npx ENOENT — Desktop bundle at ~/Library/Application Support/Genspark Claw/bin/ contains only node and electron-compat.js, no npm or npx.

OpenClaw version

Genspark Claw Desktop v0.1.655

Operating system

macOS 15.7.4 (Apple Silicon)

Install method

Genspark Claw Desktop (mac app)

Model

genspark-llm-proxy/claude-opus-4-6-1m (not model-specific, browser tool issue)

Provider / routing chain

genspark-llm-proxy (N/A — this is a browser/tooling bug, not provider-specific)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

• Affected: All Genspark Claw Desktop users wanting to use existing Chrome sessions
• Severity: High — blocks the documented user browser profile workflow entirely
• Frequency: 100% reproducible
• Consequence: Cannot use existing Chrome sessions, bookmarks, cookies, or login state with OpenClaw from Desktop, which is a significant UX gap compared to competing solutions

Additional information

Workaround: Using the managed openclaw browser profile with manual Google login inside that browser works fine.

Desktop bundle path ~/Library/Application Support/Genspark Claw/bin/ contains only node and electron-compat.js — no npm or npx. The user profile's existing-session driver tries to spawn npx chrome-devtools-mcp@latest --autoConnect which fails.

Chrome version: 147.0.7727.102 Also discussed on OpenClaw Discord #help channel.