Fix 402 retry-after misclassified as billing error

NousResearch/hermes-agent · cluster 102517 · 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 a bug where 402 responses that include retry signals (such as Retry-After headers) are incorrectly treated as terminal billing exhaustion rather than rate limits, causing unattended runs to abort prematurely. The fixes aim to correctly classify such responses and preserve retry behavior.

Open issues1

  • Issue#102517402 with Retry-After is classified as terminal billing exhaustion, aborting unattended runs

Open PRs2

  • PR#102519fix(agent): honor Retry-After and body reset fields in 402 classification
  • PR#103697fix(agent): treat 402 with retry signals as rate limit, not billing
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.