Cairn

Context length auto-detection for custom providers

NousResearch/hermes-agent · cluster 2513 · agent

Data as of

4 open items. Fix merged in #108907. Check it covers your case.

The short answer

2open issues
2open PRs
10items grouped
Known?
Yes. 10 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #108907. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #108907. That is separate from the fix event.
Still open
2 issues and 2 PRs.

These issues and pull requests address adding and fixing automatic context length detection for custom model providers, including oMLX endpoints, CLI display, fuzzy matching, and integration with models.dev for provider-aware resolution.

Open issues2

  • Issue#24640[Bug]:
  • Issue#31272[Bug]: Auto-detect context length not working correctly with oMLX

Open PRs2

  • PR#25675fix(context): read oMLX admin context window
  • PR#109603fix(dashboard): resolve the runtime provider before auto-detecting context length

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #108907 fix(cli): custom-provider wizard reports the auto-detected context length when left blank (#2513)

    merged to main

    files: hermes_cli/model_setup_flows_custom.py, tests/hermes_cli/test_custom_provider_context_feedback.py

4 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1 · duplicate 1 · other 1

  • #2514 feat: auto-detect and display context length for custom providers #2513 · closed without comment
  • #2522 fix(cli): auto-detect context length for custom providers when not specified · other → #2514, #2513
  • #83696 fix(context): read oMLX admin context window · duplicate → #25675
  • #85499 fix(cli): show context-length detection result when saving custom provider · done elsewhere → e8016a1, #108907, #2513
Closed issues · 1
  • Closed#2513[Bug]: Custom providers lack context length auto-detection when saved via /model command
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.19: 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
Merged PRs
#108907
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
12 Sep 2026

For your agent

The same facts, typed.

cluster/2513.json
cluster/2513.md