NousResearch/hermes-agent

Session resume uses wrong profile scope for custom provider

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

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

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

Read #116709 Pick up a Lab task

These issues and PRs concern a bug where multiplexed gateway session.resume incorrectly resolves or heals a custom provider against the launch profile's configuration instead of the session's own profile scope. The work addresses both deferred and cold resume paths.

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.

#116709 fix(tui-gateway): resume a secondary profile's session under its own profile scope

merged to main

files: contributors/emails/[redacted:email], tests/tui_gateway/test_resume_profile_scope.py, tui_gateway/methods_session.py

2 PRs closed without merging

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

#115614 fix(tui-gateway): resolve deferred/cold resume overrides under launch-profile scope · merged via another change → 396ab57, #116709
#116807 fix(tui-gateway): deferred/cold session.resume heals a stored custom provider against the session's own profile (#115607, salvage #115614) · duplicate → e702554, #115607

Closed issues · 1

Closed#115607[Bug]: Multiplexed gateway session.resume heals custom provider against launch profile config instead of session profile_home

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

For your agent

The same facts, typed.

cluster/115607.json
cluster/115607.md