NousResearch/hermes-agent
Ollama provider lookup and fallback handling issues
Cluster 16730 · agent. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
5items grouped
- Known?
- Yes. 5 related items grouped here, 3 issues already closed.
- Fix event
- No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMost members concern how a bare or explicit "ollama" provider is looked up and routed to a local daemon, including a report of a silent fallback to OpenRouter. One member about the model chooser and API key configuration is only loosely connected and may be a related but separate issue.
Open issues0
Open PRs0
2 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1
Closed issues · 3
- Closed#16730[Bug]: Model Chooser Conflicts with API Key Resolution and Configuration Management I think It might be related to #12146
- Closed#21352[Bug]: provider: ollama not recognized by auxiliary_client.py — silently falls back to OpenRouter
- Closed#21524[Bug]: Possible local Ollama provider resolution issue in Hermes Agent v0.12.0
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.27: 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
- agent
- Closed issues
- 3
- Attempts
- 2 PRs closed without merging