NousResearch/hermes-agent

Stale provider handling on resumed sessions

Cluster 75128 · apps/desktop. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #97008 on 28 Aug 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 #97008. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #97008 Pick up a Lab task

These items address how desktop, CLI, and TUI gateway components behave when a resumed session references a provider that has been deleted or renamed. The work focuses on falling back to current config defaults rather than failing or routing incorrectly.

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.

#97008 fix(desktop): sessions with deleted/renamed providers resume cleanly; Bot Chats follow current profile config (salvage #96111 + #90343)

merged to main

files: apps/desktop/src/plugins/hermes-bots/plugin.js, apps/desktop/src/plugins/hermes-bots/tests/group-chat.test.mjs, contributors/emails/[redacted:email], hermes_cli/runtime_provider.py, tests/hermes_cli/test_canonical_custom_identity.py, tests/test_tui_gateway_server.py, tests/tui_gateway/test_custom_provider_session_persistence.py, tests/tui_gateway/test_stale_provider_resume_live.py, tui_gateway/methods_session.py, tui_gateway/server.py

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

#78947 fix(tui-gateway): fall back to config default when resumed session's provider is gone · other → #97008, #96111
#96111 fix(tui-gateway): heal or fall back when a resumed session's provider is stale · merged via another change → #97008

Closed issues · 1

Closed#75128Desktop and CLI provider/model routing divergence after config changes

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

Subsystem: apps/desktop
Merged PRs: #97008
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 28 Aug 2026

For your agent

The same facts, typed.

cluster/75128.json
cluster/75128.md