Nothing open on GitHub. Fix merged in #113151 on 17 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113151. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113151. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where setting a per-capability backend key (e.g. for web extraction) unintentionally rerouted another capability's backend (e.g. web search). These items address identifying and fixing that misbehavior.
Open issues0
Open PRs0
Fixes on record
-
#113151 fix(web): a per-capability web backend key no longer reroutes the other capability (#113017, salvage #113046)
files:
plugins/web/firecrawl/provider.py,tests/tools/test_web_backend_capability_isolation.py,tools/web_tools.py,website/docs/user-guide/features/web-search.md
1 PR closed without merging
From the close comments: done elsewhere 1
- #113046 fix(web): per-capability backend key no longer reroutes the other capability · done elsewhere
Closed issues · 1
- Closed#113017[Bug]: setting only web.extract_backend silently changes the web_search backend
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #113151
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 17 Sep 2026