#Navigation without local browser tab
1 messages · Page 1 of 1 (latest)
That “requires a connector to my local browser” message is what happens when the agent is trying to use the chrome browser profile (the Chrome-extension relay). That mode only works if you have the OpenClaw Browser Relay extension attached to a tab (badge shows ON).
If you want it to always use the isolated OpenClaw-managed browser, force the default profile to openclaw:
1) Set the browser default profile to openclaw
In ~/.openclaw/openclaw.json:
{
browser: {
defaultProfile: "openclaw"
}
}
(or via CLI)
openclaw config set browser.defaultProfile openclaw
# then restart the gateway
After that, when the agent calls the browser tool without specifying a profile, it should use the managed browser instead of asking for a local connector.
Docs: https://docs.openclaw.ai/tools/browser (see “Profiles: openclaw vs chrome”)
2) (Optional but robust) Add an agent rule
In your agent’s AGENTS.md / system prompt, add something like:
- “When using the browser tool, always use
profile="openclaw"and never useprofile="chrome".”
3) If your gateway is on a VPS (no desktop)
The “openclaw-managed” browser runs where the gateway runs. On a headless VPS you’ll usually want a remote CDP provider (e.g. Browserless) and set that as the default profile instead (example in the same doc).