Cairn

Gateway session storage scoping and profile isolation

NousResearch/hermes-agent · cluster 48519 · gateway

Data as of

Nothing open on GitHub. Fix merged in #99770. Check it covers your case.

The short answer

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

These items concern bugs and fixes around multiplexed gateway sessions being stored in wrong profiles or incomplete storage backends (state.db vs sessions.json), plus a refactor to consolidate routing state and improve fallback behavior.

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.

  • #99770 fix(gateway): give the routing index one store instead of the ambient one (salvage #99559)

    merged to main

    files: contributors/emails/[redacted:email], gateway/session.py, tests/gateway/test_multiplex_session_db_profile_scope.py, tests/gateway/test_routing_save_fast_path.py

1 PR closed without merging

From the close comments: other 1

  • #48692 fix(gateway): fall back when agent sqlite persistence fails · other → #48519
Closed issues · 2
  • Closed#48519[BUG] Sub-profile gateway: sessions.json populated but state.db remains empty — complete session data loss (related to #40344, #46144)
  • Closed#66887Multiplexed gateway: secondary-profile Telegram sessions persist in the default profile's state.db / sessions.json (creation AND recovery paths) — config/SOUL/memory scope correctly, storage does not
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.39: 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
#99770
Closed issues
2
Attempts
1 PR closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.

cluster/48519.json
cluster/48519.md