NousResearch/hermes-agent

CLI session resume restoring correct model endpoint route

Cluster 136323 · hermes cli. Data as of 2026-10-27 11:58 UTC

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

open issues

open PRs

items grouped

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

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

Read #139947 Pick up a Lab task

These members concern CLI session resume where the stored model may be paired with the wrong provider or endpoint when no route is saved. Two titles describe state-related fixes (one a salvage of an earlier change, another about bare-custom routes and the billing endpoint), and one is a bug report describing the symptom.

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.

#139947 fix(state): resume chats on the endpoint that served them (salvage #136339)

merged to main

files: gateway/session_local_migration.py, hermes_cli/cli_model_switch_mixin.py, hermes_state_gateway.py, tests/hermes_cli/test_resume_model_restore.py, tests/tui_gateway/test_local_model_session_identity.py, tui_gateway/agent_factory.py

1 PR closed without merging

From the close comments: done elsewhere 1

#136339 fix(state): recover bare-custom CLI session routes from the billing endpoint · done elsewhere → 466c6f7, #139947

Closed issues · 1

Closed#136323[Bug]: CLI `--resume` recombines the stored model with the ambient default provider when the session row has no route (model name right, wrong backend)

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: hermes cli
Merged PRs: #139947
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 16 Oct 2026

For your agent

The same facts, typed.

cluster/136323.json
cluster/136323.md