# NousResearch/hermes-agent · Ollama local provider routing via auxiliary client

## Open now

- Nothing open on GitHub.

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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #113961. Verify it addresses your case.
- **Recommended:** read PR #113961 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-113961`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #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)

## Prior & competing PRs

- **#113961: fix(aux): provider: ollama lanes with a local base_url resolve and call the server (#106010, salvage #106018)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/auxiliary_client.py`, `tests/agent/test_auxiliary_ollama_local_provider.py`, `website/docs/user-guide/configuration.md`
- **#106018: fix(agent): route explicit local-server provider aliases (ollama/vllm) through the aux custom branch**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `5b80838ea2`, `#113961`

## Fix status

- Merged to main in PR #113961 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-17`.