NousResearch/hermes-agent

Model picker config read performance fix

Cluster 119044 · agent. Data as of

Nothing open on GitHub. Fix merged in #120404 on 23 Sep 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 #120404. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #120404. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug was identified where the model picker repeatedly re-read the config file for each model, causing timeouts with large provider catalogs. These issues and fixes address caching the config read to avoid redundant I/O in the model selection path.

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.

  • #120404 perf(picker): stop re-reading config per model and blocking on expired catalogs

    merged to main

    files: agent/models_dev.py, hermes_cli/inventory.py, hermes_cli/model_switch_providers.py, hermes_cli/models.py, providers/__init__.py, tests/hermes_cli/test_inventory.py, tests/hermes_cli/test_inventory_pricing.py, tests/hermes_cli/test_model_cache_parallel_prefetch.py, tests/providers/test_provider_registry.py

2 PRs closed without merging

From the close comments: closed without comment 1 · merged via another change 1

  • #119048 fix(inventory): avoid repeated config reads in model picker · merged via another change → #120404
  • #119609 perf(agent): cache config read in model options so large catalogs do not time out · closed without comment
Closed issues · 1
  • Closed#119044[Bug]: Model picker does O(models) config.yaml reloads via _cfg_get, times out with many providers
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
#120404
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
23 Sep 2026

For your agent

The same facts, typed.