Cairn
NousResearch/hermes-agent

OpenRouter 'Provider returned error' fallback and cooldown classification

Cluster 46856 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These items concern how an agent's error classifier handles OpenRouter's 'Provider returned error' message, which has no status code. One issue reports it being classified as unknown, so no rate-limit cooldown applies and fallback resets each turn; two pull requests propose classifying it as rate_limit and keeping the provider fallback on cooldown.

Open issues1

  • Issue#46856[Fallback] "Provider returned error" (no status code) classified as unknown → no rate-limit cooldown → fallback resets every turn

Open PRs2

  • PR#46858fix(agent): classify 'Provider returned error' as rate_limit in error classifier
  • PR#47354fix(agent): keep OpenRouter provider fallback on cooldown
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.00 means 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 Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/46856.json
cluster/46856.md