Cairn
NousResearch/hermes-agent

models.dev catalog caching and network resilience

Cluster 35838 · agent. Data as of

Nothing open on GitHub. Fix merged in #85555 on 13 Aug 2026. Check it covers your case.

The short answer

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

These items address blocking behavior and stale-cache handling when models.dev is unreachable, introducing ETag-based conditional requests, a no-network hot-path, and preferring stale cache over unsuccessful refreshes.

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.

  • #74048 fix(models): serve stale models.dev cache without blocking; keep gateway refreshes off the event loop (salvage #73621 + #35853)

    merged to main

    files: agent/agent_init.py, agent/models_dev.py, gateway/run.py, gateway/slash_commands.py, hermes_cli/providers.py, hermes_cli/route_identity.py, tests/agent/test_models_dev.py, tests/gateway/test_image_input_routing_runtime.py

  • #85555 fix(models): ETag conditional GET, no-network hot-path invariant, mirror URL override for models.dev catalog

    merged to main

    files: agent/image_routing.py, agent/models_dev.py, hermes_cli/config_defaults.py, hermes_cli/model_switch.py, hermes_cli/web_server.py, tests/agent/test_models_dev.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #35853 fix(models): use stale cache before models.dev refresh · merged via another change → a479a15, #74048, #73621
Closed issues · 1
  • Closed#35838[Bug]: `agent.models_dev.get_provider_info()` blocks when `models.dev` is unreachable and local cache is stale
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.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
Merged PRs
#74048, #85555
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
13 Aug 2026

For your agent

The same facts, typed.

cluster/35838.json
cluster/35838.md