Ollama num_ctx clamp wrongly applied to cloud providers

NousResearch/hermes-agent · cluster 99943 · agent

Data as of

5 open items. Fix attempted, not merged.

The short answer

1open issue
4open PRs
5items grouped
Known?
Yes. 5 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
1 issue and 4 PRs.

A bug caused the Ollama-specific context window clamp (ollama_num_ctx) to be incorrectly applied to non-Ollama or remote/cloud endpoints, silently reducing large context windows. Multiple fixes were proposed to gate this behavior to local Ollama runtimes only.

Open issues1

  • Issue#99943Compressor context window clamped to model.ollama_num_ctx on cloud providers — 1M window silently drops to 65,536

Open PRs4

  • PR#99953fix(agent): gate Ollama num_ctx compressor clamp on local endpoints (#99943)
  • PR#104725fix(ollama): don't apply ollama_num_ctx clamp to non-Ollama runtimes
  • PR#106756fix(agent): ignore Ollama num_ctx override on remote endpoints
  • PR#113832fix(agent): ignore leftover ollama_num_ctx on cloud sessions (#99943)
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.40: 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.