Cairn

Ollama/local provider hang and timeout issues

NousResearch/hermes-agent · cluster 17913 · agent

Data as of

9 open items. Fix attempted, not merged.

The short answer

5open issues
4open PRs
9items grouped
Known?
Yes. 9 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
5 issues and 4 PRs.

Multiple bug reports and fixes related to indefinite hangs, stream timeouts, and connection issues when using local providers like Ollama, particularly with tool definitions and custom proxy setups. Associated fixes address stream timeout scaling, context probing behavior, and toolset configuration.

Open issues5

  • Issue#17913OmniRoute compatibility: local custom providers can stall indefinitely on streamed chat completions
  • Issue#25629[Bug]: Hermes Agent + Ollama Local — Hangs indefinitely with tool definitions
  • Issue#26339[Bug] Connection reset by peer (errno 104) with Ollama local endpoint — 76KB payload rejected
  • Issue#26489Hermes hangs when provider=custom + LiteLLM proxy + Ollama (no chat completion call after probing 404s)
  • Issue#56994Requests to local Ollama models hang indefinitely with full CLI toolset (works via raw ollama run and cloud providers)

Open PRs4

  • PR#18703fix(agent): keep local stream timeouts finite
  • PR#18716fix(agent): scale stream timeouts by max_tokens output budget
  • PR#25638fix(ollama): skip local num_ctx probe for explicit chat completions
  • PR#26347fix(cli): honor legacy minimal toolset config
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.15: 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
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/17913.json
cluster/17913.md