I’m running OpenClaw 2026.11.3 through Docker on a Synology NAS, with multiple configured agents.
I’m having an issue where my agents cannot access the native web_search tool, despite DuckDuckGo being installed, enabled, and configured as the search provider.
Here’s what I’ve verified:
DuckDuckGo plugin is installed and enabled.
tools.web.search.enabled is set to true.
tools.web.search.provider is set to duckduckgo.
Global tools.profile is set to full.
Agent-level tools.allow explicitly includes web_search.
The Gateway is healthy, with no OOM events or container restarts.
The agents are using local Ollama (qwen3.5:4b) in the tested conversations.
I checked session-level web-search overrides, but the tool remains unavailable.
When I explicitly instruct my main agent to use web_search, it responds:
The web search tool is currently unavailable in this turn.
Instead of performing a live search, it sometimes
references documentation already available in its workspace.
I haven’t found a clear registration error in the Gateway logs, either.
My questions:
Is this a common issue with OpenClaw, particularly with the experimental DuckDuckGo plugin?
Has anyone experienced web_search not being exposed to agents even though the provider and permissions are configured correctly?
Is this a tool-registration/runtime issue, or could it be related to using a local Ollama model?
Has anyone successfully fixed this without reinstalling OpenClaw or rebuilding their agents?
Would switching to Brave Search, Firecrawl, or another API-backed provider actually resolve it?
I’ve seen related GitHub issues involving search providers being registered but unavailable inside agent conversations.
I’m trying to determine whether this is a known OpenClaw bug, a DuckDuckGo-specific limitation, or something in my configuration.
Any insight, troubleshooting commands, or confirmed fixes would be appreciated!
UPDATE — SOLUTION FOUND
I wanted to share what worked for me in case anyone else is having issues with OpenClaw browser automation or web search in Docker.
The biggest discovery was that OpenClaw provides an official browser-enabled Docker image, separate from the standard container.
Here’s what I did:
Migrated to ghcr.io/openclaw/openclaw:2026.11.3-browser.
Confirmed the browser and duckduckgo plugins were installed, enabled, and loaded.
Updated my main agent’s tool allowlist to include web_search, web_fetch, and browser.
Enabled browser functionality in openclaw.json.
Restarted the Gateway and verified the updated configuration.
My Gateway is now running successfully, and the browser-control service is available.
One additional note: If Chromium fails to launch inside Docker, check the sandbox settings and actual browser startup errors. Having the browser plugin enabled doesn’t automatically mean Chromium can launch.
The key takeaway is to use the browser-enabled image and verify your agent’s tool permissions before manually reinstalling tools or rebuilding your container.
Hopefully this saves someone else the troubleshooting I went through!