Cairn
NousResearch/hermes-agent

Legacy pre-0.22.1 session adoption routing in gateway

Cluster 138912 · gateway. Data as of

Nothing open on GitHub. Fix merged in #139617 on 16 Oct 2026. Check it covers your case.

The short answer

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

The members appear to share one theme: how gateway sessions created before v0.22.1 are adopted or resumed, and whether their saved model/provider routing is preserved. One is a bug report about model_config details (provider, base_url, reasoning) being dropped with an HTTP 404 reported, and two are fix-oriented changes touching legacy local routes and keeping the original route without borrowing the profile's key.

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.

  • #139617 fix(gateway): a pre-0.22.1 session adopted after the upgrade keeps its route and never borrows the profile's key

    merged to main

    files: gateway/session_local_migration.py, gateway/session_route_identity.py, tests/gateway/test_legacy_acp_route.py, tests/gateway/test_legacy_session_route_turn.py, tests/gateway/test_session_route_identity.py

1 PR closed without merging

From the close comments: won't fix / by design 1

  • #138922 fix(gateway): restore legacy local session routes · won't fix / by design
Closed issues · 1
  • Closed#138912[Bug]: adopt_legacy_session drops row['model_config'] provider/base_url/reasoning — resumed pre-v0.22.1 sessions route model to wrong provider (HTTP 404)
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.67: 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
gateway
Merged PRs
#139617
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
16 Oct 2026

For your agent

The same facts, typed.

cluster/138912.json
cluster/138912.md