202 Ratelimit for duckduckgo

[bckcolin]

I use duckduckgo as search engine， and always have "202 Ratelimit" error. How can I avoid this?

[hetaoBackend]

Thanks for the report. I checked current main, but this shell is missing enough reproduction detail to verify a current bug.

Close as stale-insufficient-info: the issue is old, has no replies, and only reports a DuckDuckGo “202 Ratelimit” without logs, environment, config, reproduction frequency, or network details. Current main still uses the DDGS-backed DuckDuckGo wrapper and offers alternate web-search providers, but there is not enough detail to reproduce or debug the DDG-specific failure.

Best possible solution:

Close this stale, low-detail report and steer affected users to the current configurable search-provider path. If the problem still reproduces on current main, the best next step is a new issue with exact reproduction steps, the original DDG/DDGS exception, DeerFlow commit/version, Python and OS versions, deployment mode, config snippet, query/frequency pattern, and network/proxy/region details.

What I checked:

• Issue context: The issue body only says the reporter uses DuckDuckGo and always sees a “202 Ratelimit” error; there are no comments, logs, versions, config snippets, network/proxy details, or reproduction steps.
• Current DDG implementation: Current main constructs a DDGS client and calls ddgs.text(), then catches all exceptions generically and returns an empty result; the report does not include the original exception/log needed to distinguish DuckDuckGo anti-abuse behavior from environment or library issues. (backend/packages/harness/deerflow/community/ddg_search/tools.py:39, ad6d934a5fd0)
• Provider workaround exists: The example config still defaults to DuckDuckGo but documents switchable Tavily, InfoQuest, Exa, and Firecrawl web_search providers, which is the practical workaround when a client is being rate-limited by DuckDuckGo. (config.example.yaml:346, ad6d934a5fd0)
• Setup wizard provider selection: The setup wizard exposes DuckDuckGo plus Tavily, InfoQuest, Exa, and Firecrawl as web search provider choices, so current setup can avoid DDG-specific rate limiting by selecting a different provider. (scripts/wizard/providers.py:169, ad6d934a5fd0)
• History check: The current DDG wrapper/default config appears in the current source import commit; the later setup-wizard work added explicit provider selection and doctor checks around search configuration. (163121d32756)

Likely related people:

• SHIYAO ZHANG: git blame and git log -S ddg_search show the current DDG search wrapper and default config lines entering the present tree in commit 163121d. The trail is a large import-style commit, so ownership confidence is medium rather than high. (role: introduced current DDG wrapper/default config in current history; confidence: medium; commits: 163121d32756; files: backend/packages/harness/deerflow/community/ddg_search/tools.py, config.example.yaml)
• DanielWalnut: Commit eef0a6e added the setup wizard and doctor command, including explicit web search provider choices and DDG/Tavily/InfoQuest/Exa/Firecrawl configuration handling. (role: recent maintainer of search-provider setup flow; confidence: medium; commits: eef0a6e2dade; files: scripts/wizard/providers.py, scripts/wizard/steps/search.py, scripts/doctor.py)
• hung_ng__: Commit 5350b2f added the Exa community search provider and config example, which is one of the current non-DDG paths relevant to avoiding DDG rate limits. (role: adjacent owner for alternate search provider work; confidence: medium; commits: 5350b2fb24b3; files: backend/packages/harness/deerflow/community/exa/tools.py, backend/tests/test_exa_tools.py, config.example.yaml)

Codex review notes: model gpt-5.5, reasoning high; reviewed against ad6d934a5fd0.