NousResearch/hermes-agent

Agent fallback logic for quota and resource errors

Cluster 73391 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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 0 PRs.

These items address how the agent handles quota exhaustion and resource limit errors, centralizing or triggering fallback behavior when worker or model limits are reached.

Open issues1

  • Issue#73391[Bug]: Worker local total request limit reached (267/32)

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: stale or abandoned 1 · superseded by another PR 1

  • #61326 fix(agent): centralize bounded model fallback · stale or abandoned → #40066
  • #73792 fix(error-classifier): trigger fallback on resource_exhausted and worker quota errors · superseded by another PR → 37ac994
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
2 PRs closed without merging

For your agent

The same facts, typed.