Keyless 403 errors disabling entire search ring
Cluster 113893. Data as of
Nothing open on GitHub. Fix merged in #131834 on 2 Oct 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 #131834. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where a single keyless vendor returning a 403 (non-rate-limit) error causes the entire keyless provider ring to stop functioning. The work involves adding failover logic so that auth rejections are handled gracefully rather than blocking all keyless search.
Open issues0
Open PRs0
Fixes on record
-
#131834 fix(web): fail over keyless auth rejections [risk 0.30]
files:
plugins/web/keyless_mcp.py,tests/tools/test_web_keyless_fallback.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#113903 fix(web): fail over keyless HTTP 403 blocks · superseded by another PR →
#131834
Closed issues · 1
- Closed#113893web_search: a pinned keyless vendor that fails with a non-rate-limit error (403) disables the whole keyless ring
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
- #131834
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Oct 2026