#how to give openclaw browser capability
1 messages · Page 1 of 1 (latest)
Short version, browser is already built in. You usually do not “grant a capability” separately, you just need the browser feature enabled and not blocked by your config.
For ~/.openclaw/openclaw.json, check these:
{
browser: {
enabled: true,
defaultProfile: "openclaw"
}
}
If you use restrictive allowlists, also make sure:
plugins.allowincludes"browser"tools.allowincludes"browser"or"group:ui"
Important: only add those if you already use plugins.allow / tools.allow. If plugins.allow excludes browser, the whole browser feature disappears.
Then restart the gateway:
openclaw gateway restart
Test it:
openclaw browser status
openclaw browser start
openclaw browser open https://example.com
For booking tickets/webinars, best practice is:
- use the isolated
openclawbrowser profile - log in manually yourself
- do not give the model your passwords
- expect some sites to require you to solve CAPTCHA / 2FA / payment confirmation
If you want it to use your already signed-in real browser session instead, use the user profile, but that works best when you are at the computer.
If your agent runs in a sandbox and you want it to control the host browser, also enable:
{
agents: {
defaults: {
sandbox: {
browser: {
allowHostControl: true