NousResearch/hermes-agent
Cron fallback provider receives primary model instead of fallback entry's model
Cluster 47781 · cron. Data as of
1 open item. Fix attempted, not merged.
The short answer
1open issue
0open PRs
5items grouped
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 3 PRs 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 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMost members describe the same reported problem: when cron falls back to another provider, it appears to keep the primary model rather than use the model from the fallback_providers entry, which is linked to a 404 for an unknown model. The cluster includes bug reports and proposed fixes, plus one related feature proposal for model-pinned fallback entries (require_same_model, match_model).
Open issues1
- Issue#47781[Bug]: cron fallback ignores model from fallback_providers entry, sends primary model to fallback provider
Open PRs0
3 PRs closed without merging
From the close comments: other 3
Closed issues · 1
- Closed#60847bug(cron): fallback switches provider but keeps primary model — fallback provider gets unknown model, 404
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.44: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- cron
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging