Cairn
NousResearch/hermes-agent

Fix MoA selection and routing inconsistencies in CLI

Cluster 71244 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These members address bugs where bare '-m moa' and related MoA selection commands produce 404 errors or fail inconsistently. The fixes aim to resolve MoA references to a default preset and handle edge cases like switching when already on MoA.

Open issues1

  • Issue#71244MoA selection inconsistencies: bare '-m moa' 404s, and '/model moa --global' fails when already on MoA

Open PRs1

  • PR#71289fix(cli): resolve bare MoA selections consistently

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #71399 fix(cli): resolve bare -m moa to default preset instead of 404 · superseded by another PR → #71289
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.67: 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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/71244.json
cluster/71244.md