Profile sessions stored in wrong state.db location
Cluster 88532. Data as of
Nothing open on GitHub. Fix merged in #88734 on 17 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #88734. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #88734. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug caused multiplexed gateway sessions to be written to the root/default state.db instead of the owning profile's database. These items address identifying and fixing the session DB path resolution to respect the active profile scope.
Open issues0
Open PRs0
Fixes on record
-
#88734 fix(gateway): multiplex sessions now stored in the owning profile's state.db, not root (#88532, salvage #88632)
files:
gateway/run.py,gateway/session.py,tests/gateway/test_multiplex_session_db_profile_scope.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#88632 fix(gateway): resolve the session DB inside the active profile scope · merged via another change →
#88734,#88532
Closed issues · 1
- Closed#88532Bug: a profile's sessions are physically stored in the default/root state.db (profile_name correct) — desktop shows them under the default/hermes bot
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.00means 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 LabAt a glance
- Merged PRs
- #88734
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 17 Aug 2026