Reclassify WAF/Cloudflare 403s away from auth errors
Cluster 70566 · agent. Data as of
Nothing open on GitHub. Fix merged in #115812 on 19 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 #115812. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115812. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address the misclassification of WAF and Cloudflare challenge responses (HTTP 403s) as authentication or API key failures. The work involves correctly identifying these as firewall or upstream blocks rather than rejected credentials.
Open issues0
Open PRs0
Fixes on record
-
#115812 fix(providers): WAF 403s report as a firewall block, not a rejected key; anthropic_messages routes send custom extra_headers (#24293, #9721, #53099, #70566, salvage #46002 #70567 #53114)
files:
agent/agent_runtime_helpers.py,agent/anthropic_adapter.py,agent/error_classifier.py,agent/error_surface.py,agent/turn_failure_copy.py,agent/turn_recovery.py,apps/desktop/src/i18n/en.ts,apps/desktop/src/lib/error-surface.test.ts,apps/desktop/src/lib/error-surface.ts,cli.py,cron/scheduler_failure_copy.py,hermes_cli/cli_chat_error_copy.py,tests/agent/test_anthropic_adapter_extra_headers.py,tests/agent/test_error_classifier.py,tests/agent/test_error_classifier_upstream_blocked.py,tests/agent/test_run_agent_codex_responses.py,tests/cron/test_cron_failure_notice_copy.py,tests/hermes_cli/test_single_query_exit_contract.py,tui_gateway/user_messages.py,ui-tui/src/app/userMessages.ts(+1 more)
1 PR closed without merging
From the close comments: merged via another change 1
-
#70567 fix(agent): classify Cloudflare challenges as upstream · merged via another change →
cb062f7,#115812,#24293,#9721,#53099,#70566,#46002,#70567,#53114
Closed issues · 1
- Closed#70566Cloudflare challenge 403s are misclassified as authentication failures
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
- Subsystem
- agent
- Merged PRs
- #115812
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026