Tell agent how to use browser

[lucid cypress]

I have an agent that I asked him to use browser and they said they didn't have a browser to use. My 'openclaw browser status' shows everything is connected correctly so openclaw can use browser. What do I have to do to tell agent how to use browser?

[quasi wyvern]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[craggy vapor]

First, paste openclaw --version.

Short answer, you usually do not teach it in the prompt. openclaw browser status only proves the browser service is healthy. The agent still needs the browser tool in its effective tool policy.

Most likely issue: the agent is on tools.profile: "coding" (the common default), and that profile does not include browser. browser lives under group:ui.

What to check:

1. Tool policy

   {
     tools: {
       profile: "coding",
       alsoAllow: ["browser"],
     },
   }
   

Or per agent:

{
  agents: {
    list: [
      {
        id: "main",
        tools: {
          profile: "coding",
          alsoAllow: ["browser"],
        },
      },
    ],
  },
}

2. Deny lists
   Make sure none of these block it:

   • tools.deny
   • agents.list[].tools.deny
   • sandbox/group tool policy

3. Plugin allowlist
   If you use plugins.allow, it must include browser.

4. If this is an ACP agent (Codex, Claude Code, Gemini CLI)
   ACPX sessions do not expose OpenClaw plugin tools by default, so that can also explain it.

Good docs:

• https://docs.openclaw.ai/tools/browser
• https://docs.openclaw.ai/help/troubleshooting
• https://docs.openclaw.ai/gateway/configuration-reference

If you paste these, I can tell you the exact fix:

openclaw --version
openclaw config get tools
openclaw config get agents
openclaw config get plugins.allow

[lucid cypress]

$ openclaw config get tools

🦞 OpenClaw 2026.4.14 (unknown) — iMessage green bubble energy, but for everyone.

{
"profile": "coding",
"web": {
"search": {
"enabled": true,
"provider": "ollama",
"openaiCodex": {}
},
"fetch": {
"enabled": true
}
},
"exec": {
"host": "gateway",
"security": "full",
"ask": "off"
}
}
node@af97fcfa17f4:~/.openclaw$ openclaw config get plugins.allow

🦞 OpenClaw 2026.4.14 (unknown) — Like having a senior engineer on call, except I don't bill hourly or sigh audibly.

[
"discord",
"browser",
"openai",
"openrouter",
"ollama",
"memory-core",
"nano-gpt"
]

The specific agent I am talking with is

{
"id": "jim-ceo",
"name": "jim-ceo",
"workspace": "/home/node/.openclaw/workspace/aurora",
"agentDir": "/home/node/.openclaw/agents/aurora/agent",
"identity": {
"name": "Jim - CEO",
"theme": "AI Assistant",
"emoji": "🌙"
}
},

[craggy vapor]

Yep, that confirms it.

Your browser plugin is loaded correctly, but your tool policy is blocking it.

The key line is:

{
  "profile": "coding"
}

coding does not include browser. browser is in group:ui, so the agent never sees that tool even though openclaw browser status is healthy.

Fix

Add browser to the agent’s effective tools.

Easiest global fix

{
  tools: {
    profile: "coding",
    alsoAllow: ["browser"]
  }
}

Better, only for jim-ceo

{
  agents: {
    list: [
      {

        id: "jim-ceo",
        tools: {
          profile: "coding",
          alsoAllow: ["browser"]
        }
      }
    ]
  }
}

Then restart the gateway.

Important

Use alsoAllow, not allow.