NousResearch/hermes-agent
Subscription 429 locking sole credential via uncapped cooldown
Cluster 119163 · agent. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
4items grouped
- Known?
- Yes. 4 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 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug where an absolute reset_at timestamp from a subscription-period 429 response bypasses the intended short cooldown, potentially locking the only available credential for an extended period. The related items are fixes that cap or clamp the persisted cooldown to prevent this excessive lockout.
Open issues1
- Issue#119163[Bug]: an absolute last_error_reset_at from a subscription-period 429 bypasses the sole-credential short cooldown — one valid key locked out for ~15 days
Open PRs1
- PR#119652fix(agent,hermes_cli): re-probe a lone rate-limited credential and consolidate pool/fallback cooldown fixes
2 PRs closed without merging
From the close comments: superseded by another PR 1 · other 1
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.50: 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
- 2 PRs closed without merging