Remote Gateway + Chrome Extension: CLI sees Tabs, Agent sees no Tabs
Hi,
I'm running into an issue with the Chrome Extension setup and would love some help.
Setup:
- OpenClaw Gateway on a VPS (Ubuntu, bind=loopback, port 18789)
- Node Host running on a Mac, connected via SSH tunnel (ssh -N -L 18789:127.0.0.1:18789)
- Chrome Extension installed on the Mac, badge shows "ON" on the desired tab
- Version: 2026.3.2
What works:
- Node Host connects successfully (paired · connected, caps: browser, system)
-
-
- Extension relay is running on Mac port 18792
- Gateway token correctly set in extension options
What doesn't work:
- The agent (Web Dashboard) always responds: "Chrome Relay Extension is running but no tab is connected"
- Even with explicit
-
- The VPS automatically starts its own openclaw process on port 18792
What we already tried:
- gateway.nodes.browser.mode set to auto and manual
- gateway.nodes.browser.node pinned to the Mac's node ID
- agents.defaults.sandbox.browser.allowHostControl = true
- tools.sandbox.tools.allow = ["browser"] and deny list without browser
- browser.defaultProfile = chrome
- Reverse SSH tunnel -R 18795:127.0.0.1:18792
- Created new profile mychrome on port 18795
- gateway.mode = local
- openclaw doctor --repair
- Extension reloaded multiple times, tab reconnected
The CLI can see the tabs fine, but the agent cannot. How do we fix this?
I'm running into an issue with the Chrome Extension setup and would love some help.
Setup:
- OpenClaw Gateway on a VPS (Ubuntu, bind=loopback, port 18789)
- Node Host running on a Mac, connected via SSH tunnel (ssh -N -L 18789:127.0.0.1:18789)
- Chrome Extension installed on the Mac, badge shows "ON" on the desired tab
- Version: 2026.3.2
What works:
- Node Host connects successfully (paired · connected, caps: browser, system)
-
openclaw browser tabs --browser-profile chrome-
openclaw browser profileschrome: running (2 tabs), port: 18792- Extension relay is running on Mac port 18792
- Gateway token correctly set in extension options
What doesn't work:
- The agent (Web Dashboard) always responds: "Chrome Relay Extension is running but no tab is connected"
- Even with explicit
profile='chrome'target='host'-
openclaw browser snapshot --browser-profile chrome- The VPS automatically starts its own openclaw process on port 18792
What we already tried:
- gateway.nodes.browser.mode set to auto and manual
- gateway.nodes.browser.node pinned to the Mac's node ID
- agents.defaults.sandbox.browser.allowHostControl = true
- tools.sandbox.tools.allow = ["browser"] and deny list without browser
- browser.defaultProfile = chrome
- Reverse SSH tunnel -R 18795:127.0.0.1:18792
- Created new profile mychrome on port 18795
- gateway.mode = local
- openclaw doctor --repair
- Extension reloaded multiple times, tab reconnected
The CLI can see the tabs fine, but the agent cannot. How do we fix this?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,426Members
Resources
Similar Threads
Was this page helpful?
