NousResearch/hermes-agent

Ollama local provider routing via auxiliary client

Cluster 106010. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #113961 on 17 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #113961. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #113961. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #113961, then check it covers your case.

Read #113961 Pick up a Lab task

These items concern a bug where auxiliary configurations using provider: ollama with a local base URL incorrectly trigger an API key error, and related fixes to route local-server provider aliases (ollama/vllm) through the correct auxiliary custom branch.

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.

#113961 fix(aux): provider: ollama lanes with a local base_url resolve and call the server (#106010, salvage #106018)

merged to main

files: agent/auxiliary_client.py, tests/agent/test_auxiliary_ollama_local_provider.py, website/docs/user-guide/configuration.md

1 PR closed without merging

From the close comments: merged via another change 1

#106018 fix(agent): route explicit local-server provider aliases (ollama/vllm) through the aux custom branch · merged via another change → 5b80838, #113961

Closed issues · 1

Closed#106010[Bug]: auxiliary `provider: ollama` + local base_url + empty api_key raises "no API key was found" since the auxiliary_client refactor (worked before; `provider: custom` still works)

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

Merged PRs: #113961
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 17 Sep 2026

For your agent

The same facts, typed.

cluster/106010.json
cluster/106010.md