NousResearch/hermes-agent

Custom-provider model lock identity mismatch corrections

Cluster 116070. Data as of 2026-10-24 13:18 UTC

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

open issues

open PRs

items grouped

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

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

Read #116752 Pick up a Lab task

These items address a bug where model locks for user-configured (custom) providers consistently encountered errors due to a mismatch between the looked-up family name and the stored slug. Multiple corrections and a diagnosis note cover the same underlying identity-comparison problem.

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.

#116752 fix(api-server): custom-provider model locks no longer fail every completed turn (#116070, salvage #116076)

merged to main

files: gateway/platforms/api_server.py, tests/gateway/test_session_api.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

#116076 fix(api-server): keep custom-provider model locks from failing completed turns · merged via another change → 12c1ccb, #116752, #116070, #116076
#116128 fix(api-server): accept equivalent custom-provider model lock identities · done elsewhere → 12c1ccb, #116752, #116070, #116076

Closed issues · 1

Closed#116070api_server: confirmed model lock always mismatches for user-configured (custom) providers — resolved family name vs stored slug

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.50: 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: #116752
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/116070.json
cluster/116070.md