Misclassified content-moderation 400 error handling
Cluster 115218. Data as of
Nothing open on GitHub. Fix merged in #116670 on 20 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 #116670. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116670. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A provider 400 error with 'Content Exists Risk' is being incorrectly classified as a malformed request rather than a content-policy block, causing broken fallback behavior in bot-mode and subagents. These items address detecting and correctly routing that specific error code.
Open issues0
Open PRs0
Fixes on record
-
#116670 fix(agent): provider content-moderation 400 (Content Exists Risk) is reported as a safety-filter refusal, not a malformed request (#115218, salvage #115233)
files:
agent/error_classifier.py,tests/agent/test_error_classifier.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#115233 fix(agent): classify CommandCode "Content Exists Risk" 400 as a content-policy block · done elsewhere →
d4f88f3,#116670
Closed issues · 1
- Closed#115218[Bug]: Provider content-moderation 400 (`Content Exists Risk`) has no fallback path — bot-mode delivery fails closed, subagents are killed, and the message says "malformed"
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
- #116670
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026