From b1d4f2033c17e412068570b1feed391c93bb9d1f Mon Sep 17 00:00:00 2001 From: asto18089 Date: Wed, 9 Sep 2026 18:53:52 +0800 Subject: [PATCH] docs(changelog): record keyless Bing search tail The copy half of this PR - the web_search module doc, the tool description, and the all-backends-down provider list - was absorbed upstream in evolved, tested form by "fix(search): preserve reachable API fallback" and "fix(search): restore actionable backend guidance", which route API-backed providers directly to the keyless Bing tail and name the keyed providers plus keyless routes in the configuration hint. What stays missing on pinvou3-clean is the CHANGELOG record for that switch: [Unreleased] had no entry for it. Adapt the original entry to the current chain (keyless Firecrawl default, direct keyless Bing tail, keyed-provider configuration hint) and place it under [Unreleased]. Signed-off-by: asto18089 --- CHANGELOG.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4ab4760129..9a7e60c6e3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +### Fixed + +- API-backed `[search]` providers now visibly degrade directly to the + keyless Bing tail instead of routing through DuckDuckGo when + unavailable: DuckDuckGo is unreachable from mainland-China networks + (DNS poisoning plus SNI reset), while Bing serves its global and China + endpoints without a key. The all-backends-down guidance names every + keyed provider (tavily, bocha, metaso, baidu, volcengine, sofya) and + the keyless routes (firecrawl, bing), and the `web_search` tool + description no longer claims a DuckDuckGo hop for configured API + backends. + ## [0.9.12] - 2026-09-04 Codewhale v0.9.12 puts computer use in the binary, opens two new routes —