NousResearch/hermes-agent

Desktop profile isolation and state.db binding fixes

Cluster 102315. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #108074 on 11 Sep 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 #108074. 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 #108074, then check it covers your case.

Read #108074 Pick up a Lab task

These items address bugs where desktop sessions could incorrectly bind to or report another profile's state.db, and work to pin backend child processes to the correct profile home. The focus is on profile isolation for desktop child processes, particularly on Windows.

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.

#108074 Sessions no longer bind to or read another profile's state.db (#102526, #106761, #105887, #106974; salvage #102534, #106975)

merged to main

files: agent/turn_explainers.py, agent/turn_finalizer.py, evals/session_search_schema/runner.py, hermes_cli/profiles.py, hermes_state_registry.py, tests/hermes_cli/test_deleted_profile_tombstone.py, tests/hermes_state/test_shared_session_db_registry.py, tests/run_agent/test_corruption_recovery_guidance.py, tests/tools/test_session_search.py, tests/tui_gateway/test_launch_db_home_override_race.py, tests/tui_gateway/test_session_resume_db_ownership.py, tools/session_search_tool.py, tui_gateway/server.py

1 PR closed without merging

From the close comments: done elsewhere 1

#102343 fix(desktop): pin backend children to the Hermes-root HERMES_HOME · done elsewhere → #102315, #108074

Closed issues · 1

Closed#102315[Bug]: Windows Desktop child can report --profile default while using another profile home/state.db

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

Merged PRs: #108074
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 11 Sep 2026

For your agent

The same facts, typed.

cluster/102315.json
cluster/102315.md