Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix web_search cannot find Brave provider after upgrade to 2026.5.3 despite valid Brave plugin and API key [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#77737•Fetched 2026-05-06 06:22:14
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
samihaosamihao
Participants
clawsweeper[bot]clawsweeper[bot]samihaosamihao
Timeline (top)
closed ×1commented ×1labeled ×1

web_search provider brave configured and plugin loaded, but tool returns no provider available

Root Cause

web_search provider brave configured and plugin loaded, but tool returns no provider available

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

web_search provider brave configured and plugin loaded, but tool returns no provider available

Steps to reproduce

  1. Start OpenClaw 2026.5.3 with web search enabled and Brave configured:

    tools.web.search.enabled = true tools.web.search.provider = "brave" plugins.entries.brave.enabled = true plugins.entries.brave.config.webSearch.apiKey is present

  2. Confirm @openclaw/brave-plugin is installed and enabled.

  3. Restart the Gateway/container.

  4. Ask the agent to use web_search, for example: "Search OpenAI ChatGPT release notes."

  5. Observe that the managed web_search tool fails with: "web_search is disabled or no provider is available."

  6. Verify the same Brave API key works outside the managed tool by calling Brave Search API directly; it returns 200 OK and valid results.

Expected behavior

When tools.web.search.provider is set to "brave" and the Brave plugin/API key are configured, the agent should expose and use the managed web_search tool with provider "brave".

web_search should return Brave search results instead of reporting that no provider is available.

Actual behavior

web_search fails with:

"web_search is disabled or no provider is available."

However, the Brave plugin is installed and enabled, tools.web.search.provider is set to "brave", and the configured Brave API key works when called directly. A direct Brave API fallback returns valid search results with provider "brave".

OpenClaw version

2026.5.3

Operating system

Docker container on macOS host Container OS: Linux 6.12.76-linuxkit x64 Node.js: v24.14.0

Install method

Docker / docker compose

Model

openai-codex/gpt-5.5

Provider / routing chain

openai-codex/gpt-5.5

Additional provider/model setup details

Relevant config:

tools.web.search.enabled = true tools.web.search.provider = "brave" plugins.entries.brave.enabled = true plugins.entries.brave.config.webSearch.apiKey is present @openclaw/brave-plugin version = 2026.5.3

Test result from managed tool: web_search -> "web_search is disabled or no provider is available."

Direct Brave API test using the same configured key returns 200 OK and valid results.

Steps already tried:

  • Restarted Gateway/container
  • Reinstalled @openclaw/brave-plugin
  • Ran doctor --fix
  • Refreshed plugin registry
  • Confirmed Brave API key works directly

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue might be resolved by verifying the compatibility of the @openclaw/brave-plugin version with OpenClaw 2026.5.3 and ensuring the plugin is correctly loaded.

Guidance

  • Check the @openclaw/brave-plugin version and verify it is compatible with OpenClaw 2026.5.3.
  • Confirm that the plugins.entries.brave.config.webSearch.apiKey is correctly set and accessible by the web search tool.
  • Review the plugin loading process to ensure that the Brave plugin is loaded after the web search tool is enabled.
  • Test the web search tool with a different provider to isolate if the issue is specific to the Brave provider.

Example

No code snippet is provided as the issue seems to be related to configuration and plugin compatibility.

Notes

The issue might be related to a version mismatch or a loading order issue, but without more information about the plugin and OpenClaw versions, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Verify the plugin version and loading order, and test with a different provider to isolate the issue. This approach allows for a more targeted investigation without requiring an immediate version upgrade.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When tools.web.search.provider is set to "brave" and the Brave plugin/API key are configured, the agent should expose and use the managed web_search tool with provider "brave".

web_search should return Brave search results instead of reporting that no provider is available.

#api#integration issue#index setup#retrieval issue#search optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix web_search cannot find Brave provider after upgrade to 2026.5.3 despite valid Brave plugin and API key [1 comments, 2 participants]