openclaw - 💡(How to fix) Fix web_search broken — DuckDuckGo returns bot detection since 2026-03-30 [1 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#59220Fetched 2026-04-08 02:27:21
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Error Message

Error:

RAW_BUFFERClick to expand / collapse

Bug: web_search broken — DuckDuckGo returns bot detection since 2026-03-30

Severity: HIGH

First logged: 2026-03-30 Last logged: 2026-03-31

Description: All web_search calls fail with "DuckDuckGo returned a bot-detection challenge" starting 2026-03-30T18:44. This blocks x:daily-post, research tasks, and any automation that depends on web search.

Error:

Impact:

  • x:daily-post workflow cannot complete (depends on web_search for content)
  • Research automation is down
  • No fallback backend currently configured

Expected behavior: web_search should return results reliably. Need an alternative search backend (Tavily, Brave Search, SerpAPI) as a fallback when DuckDuckGo is blocked.

Environment: macOS, OpenClaw v2026.3.13

Suggested fix: Add a configurable search backend option (e.g., Tavily or Brave Search) as fallback when DuckDuckGo fails bot detection.

extent analysis

TL;DR

Implement a fallback search backend, such as Tavily or Brave Search, to replace or supplement DuckDuckGo when bot detection fails.

Guidance

  • Investigate the bot detection challenge returned by DuckDuckGo to understand the specific requirements for passing the challenge.
  • Configure a secondary search backend, like Tavily or Brave Search, as a fallback option when the primary backend (DuckDuckGo) fails.
  • Consider implementing a rotating or randomizing user agent in the web_search calls to mitigate bot detection.
  • Evaluate the feasibility of integrating SerpAPI as an alternative or additional search backend for improved reliability.

Example

No explicit code example is provided due to the lack of specific implementation details in the issue.

Notes

The exact implementation of the fallback search backend may vary depending on the specific requirements and constraints of the project, including the compatibility of the alternative search backends with the existing web_search functionality.

Recommendation

Apply a workaround by implementing a fallback search backend, as this allows for continued functionality of critical workflows like x:daily-post and research tasks while a more permanent solution to the DuckDuckGo bot detection issue is explored.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING