#πŸ› Bug: EasyClaw (Browser Relay) Chrome Extension β€” Google Sign-in Fails**Environment:**- Genspar

1 messages Β· Page 1 of 1 (latest)

fossil flume
#

πŸ› Bug: EasyClaw (Browser Relay) Chrome Extension β€” Google Sign-in Fails

Environment:

  • Genspark Claw Desktop v0.1.655
  • macOS 15.7.4 (Apple Silicon)
  • Chrome 147.0.7727.102

Steps to Reproduce:

  1. Install "OpenClaw Browser Relay β€” EasyClaw" Chrome extension
  2. Click extension icon β†’ shows "Not connected" + "Sign in" button
  3. Click "Sign in" β†’ "Continue with Google"
  4. Google OAuth completes but returns an error page
  5. Extension remains "Not connected", no tabs visible to Gateway

Expected: Extension connects after Google sign-in
Actual: Error after OAuth callback, extension stays disconnected

Workaround: Used OpenClaw managed browser (openclaw profile) with manual Google login

Impact: Cannot use existing Chrome sessions (bookmarks, login state) with OpenClaw β€” significant UX gap

raven rockBOT
sudden brookBOT
#

I think you’re hitting the old Chrome extension path.

Current OpenClaw docs say the extension-based browser relay was removed, and the supported way to use your real Chrome session is the built-in user browser profile via Chrome DevTools MCP, not the EasyClaw Google sign-in flow.

Can you paste:

  • openclaw --version
  • the exact text / URL from the OAuth error page

What I’d try now:

  1. Don’t use the EasyClaw extension
  2. Use the browser user profile instead
  3. In Chrome 144+, open chrome://inspect/#remote-debugging
  4. Enable remote debugging, keep Chrome running, and accept the attach prompt
  5. Run the doctor check, it specifically migrates old extension-based browser config and checks Chrome attach readiness
fossil flume
#

Thanks! We actually tried the user profile first, but got:
"Chrome MCP existing-session attach failed β€” Error: spawn npx ENOENT"

npx is not available in the Genspark Claw Desktop environment
(only node is bundled at <a class="file-link" data-path="/Users/user/Library/Application Support/Genspark Claw/users/Library/Application" title="γ‚―γƒͺックして開く">~/Library/Application</a> Support/Genspark Claw/bin/node,
no npm/npx).

Chrome 147, remote debugging was enabled at chrome://inspect/#remote-debugging.

Is npx expected to be bundled with Genspark Claw Desktop,
or do we need to install Node.js separately?

sudden brookBOT
#

Yep, for the current user / existing-session path, npx is expected.

The browser docs explicitly say OpenClaw uses Chrome DevTools MCP and that the gateway/node host can spawn:

npx chrome-devtools-mcp@latest --autoConnect

So this error:

spawn npx ENOENT

basically means the Desktop build can’t find npx, even though Chrome 147 + remote debugging are fine.

Short answer:

  • Yes, installing Node.js separately is the current workaround
  • Also yes, this looks like a Desktop packaging bug/regression if it ships node but not npm/npx
#

Practical options right now:

  1. Keep using the managed openclaw profile
  2. Install Node.js so npx is available, then retry the user profile

One macOS gotcha: GUI apps sometimes don’t see your shell PATH, so even after installing Node, the Desktop app may still miss npx unless its PATH/environment is set up correctly.

Docs:

Please add this exact detail to a GitHub issue too, including:

  • openclaw --version
  • spawn npx ENOENT
  • Desktop version v0.1.655

Issue tracker: https://github.com/openclaw/openclaw/issues

fossil flume
#

Thanks for the detailed reply! I don't have a GitHub account β€” could you (or someone from the team) file this as an issue on my behalf?

Here's the info:

  • Genspark Claw Desktop v0.1.655
  • macOS 15.7.4 (Apple Silicon)
  • Chrome 147.0.7727.102
  • Error: spawn npx ENOENT when using user profile
  • Desktop bundles node but not npm/npx
  • Path: <a class="file-link" data-path="/Users/user/Library/Application Support/Genspark Claw/users/Library/Application" title="γ‚―γƒͺックして開く">~/Library/Application</a> Support/Genspark Claw/bin/ (only node + electron-compat.js)

Happy to provide any additional details if needed. Thanks! πŸ™

sudden brookBOT
#

I can’t open GitHub issues on someone’s behalf from here, sorry, read-only policy on my side.

But I can give you a clean ready-to-paste issue so anyone with an account can relay it:

Title
Desktop cannot use existing Chrome sessions: EasyClaw Google sign-in fails, and user profile attach fails with spawn npx ENOENT

Body

## Summary

On Genspark Claw Desktop, I cannot use my existing Chrome session with OpenClaw.

Two different paths fail:

1. **EasyClaw / Browser Relay Chrome extension**
# 
   - Google sign-in completes, then returns an error page
   - Extension remains "Not connected"
   - No tabs become visible to the Gateway

2. **Built-in `user` browser profile**
   - Existing-session attach fails with:
     `Chrome MCP existing-session attach failed β€” Error: spawn npx ENOENT`

## Environment

- Genspark Claw Desktop v0.1.655
- macOS 15.7.4 (Apple Silicon)
- Chrome 147.0.7727.102

## Repro 1: EasyClaw extension Google sign-in fails
# 

### Steps
1. Install the "OpenClaw Browser Relay β€” EasyClaw" Chrome extension
2. Click extension icon
3. See "Not connected" and click "Sign in"
4. Choose "Continue with Google"
5. Google OAuth completes
6. Callback lands on an error page

### Expected
Extension connects and exposes current Chrome tabs to OpenClaw

### Actual
Extension stays disconnected and no tabs are visible
# 
## Repro 2: `user` profile fails with missing npx

### Steps
1. Try to use the built-in `user` profile for existing Chrome session attach
2. Chrome 147 is running locally
3. Remote debugging is enabled at `chrome://inspect/#remote-debugging`

### Expected
OpenClaw attaches to the running Chrome session

### Actual
Attach fails with:
`spawn npx ENOENT`

## Notes
# 

Desktop bundle appears to include:
- `node`
- `electron-compat.js`

But not:
- `npm`
- `npx`

Observed bundle path:
`~/Library/Application Support/Genspark Claw/bin/`

## Workaround

Using the managed `openclaw` browser profile works, with manual Google login inside that managed browser.