NousResearch/hermes-agent

MoA fallback model resolution and persistence errors

Cluster 112525. Data as of

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

These issues and fixes address a bug where using a MoA preset as a fallback model causes the preset name to be stored instead of the looked-up aggregator slug. Multiple fix attempts refine how the computed MoA model identity is preserved through the fallback chain.

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.

  • #113131 fix(agent): a MoA preset in the fallback chain runs the preset, not the aggregator with a virtual identity (#112525, #112623, supersedes #112528 #112532 #112629)

    merged to main

    files: agent/agent_init.py, agent/agent_runtime_helpers.py, agent/chat_completion_helpers.py, agent/moa_loop.py, tests/agent/test_provider_fallback.py, website/docs/user-guide/features/fallback-providers.md, website/docs/user-guide/features/mixture-of-agents.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/features/fallback-providers.md

2 PRs closed without merging

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

  • #112528 fix(agent): preserve resolved MoA fallback model · merged via another change → #113131
  • #112532 fix(agent): persist resolved fallback model, not the MoA preset name · superseded by another PR → c810640, #113131, #112525, #112623
Closed issues · 1
  • Closed#112525[Bug]: fallback to provider=moa keeps the preset name as agent.model — the resolved aggregator slug is discarded
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

Merged PRs
#113131
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
17 Sep 2026

For your agent

The same facts, typed.