Cairn

Rate-limit cooldown should use provider reset window

NousResearch/hermes-agent · cluster 117484

Data as of

Nothing open on GitHub. Fix merged in #117604. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #117604. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #117604. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern a bug where the rate-limit fallback cooldown uses an exponential backoff guess instead of the provider's own reset timestamp, which is parsed but then discarded. The work focuses on making the cooldown honor the provider-supplied reset time.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #117604 fix(agent): rate-limit cooldown honours the provider's reset window instead of an exponential guess (#117484, salvage #117503)

    merged to main

    files: agent/chat_completion_helpers.py, agent/fallback_cooldown.py, agent/turn_api_error.py, agent/turn_recovery.py, hermes_cli/config_defaults.py, hermes_cli/web_server_config.py, tests/agent/test_provider_reset_cooldown.py, website/docs/user-guide/features/fallback-providers.md

4 PRs closed without merging

From the close comments: done elsewhere 2 · merged via another change 1 · superseded by another PR 1

  • #117493 fix(agent): honor provider rate-limit reset cooldown · superseded by another PR → #117504, #117518
  • #117503 fix(agent): keep fallback aligned with provider reset windows · merged via another change → dcae0d8, #117604
  • #117504 fix(agent): honor provider reset_at in rate-limit cooldown · done elsewhere → dcae0d8, #117604
  • #117518 Honor the provider's own rate-limit reset window when arming fallback cooldown · done elsewhere → dcae0d8, #117604
Closed issues · 1
  • Closed#117484[Bug]: The rate-limit cooldown guesses the wait exponentially while the provider's own reset time is parsed a few lines earlier and dropped
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.33: 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

Merged PRs
#117604
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
21 Sep 2026

For your agent

The same facts, typed.

cluster/117484.json
cluster/117484.md