NousResearch/hermes-agent
OpenRouter guardrail error pattern matching fix
Cluster 133850 · agent. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug was identified where OpenRouter's reworded guardrail 404 responses no longer matched the existing pattern used to classify them as provider_policy_blocked, causing unwanted retries. The fix updates the pattern matching to recognize the new error wording.
Open issues1
- Issue#133850[Bug]: OpenRouter guardrail 404s are retried 3x instead of falling back: new error wording no longer matches _PROVIDER_POLICY_BLOCKED_PATTERNS
Open PRs1
- PR#133877fix(agent): match OpenRouter reworded guardrail 404 as provider_policy_blocked
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#134325 fix(agent): recognize OpenRouter guardrail failures · superseded by another PR →
#133877
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
- Closed issues
- 0
- Attempts
- 1 PR closed without merging