Repeated config/credential disk reads causing slowness

NousResearch/hermes-agent · cluster 31556 · agent/secret sources

Data as of

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

The short answer

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

Multiple efforts to cache or memoize config and credential loading functions that are called dozens of times during model picker discovery, causing significant latency. The work spans CLI, credential pool, and config layers.

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.

  • #74294 fix(cron): scrub ALL GitHub auth-header curl blocks — multi-skill cron jobs no longer false-block (salvage #31671)

    merged to main

    files: tests/tools/test_cronjob_tools.py, tools/cronjob_tools.py

3 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1 · superseded by another PR 1

  • #31587 fix(cli): cache load_config() during /model picker discovery · stale or abandoned
  • #31671 perf(credential-pool): cache _load_config_safe() result to avoid 69× deepcopy · done elsewhere → 9b8b054, #74294
  • #85850 perf(model_switch): memoise config and credential-pool loads in list_authenticated_providers · superseded by another PR
Closed issues · 2
  • Closed#31556[Performance] /model picker takes ~17s due to load_config() called 69 times
  • Closed#59055Centralize Config Propagation and Cache Disk-Read Operations
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: 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/secret sources
Merged PRs
#74294
Closed issues
2
Attempts
3 PRs closed without merging
Fix link checked
29 Jul 2026

For your agent

The same facts, typed.