Lazy TUI state path resolution and test isolation

NousResearch/hermes-agent · cluster 112692

Data as of 2026-10-23 11:54 UTC

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

open issues

open PRs

items grouped

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

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

Read #113224 Pick up a Lab task

These items address a timing problem where the TUI gateway computed its state store path at import time rather than first use, causing test errors when the test sandbox was not yet established. The fixes defer path resolution and isolate the test suite from any live Hermes installation on the developer's machine.

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.

#113224 fix(tui_gateway): launch state.db home resolves at first use and the test harness sandboxes the Windows production root (#112692, salvage #112799)

merged to main

files: tests/conftest.py, tests/tui_gateway/test_launch_db_home_override_race.py, tui_gateway/server.py

3 PRs closed without merging

From the close comments: PR volume cleanup 1 · superseded by another PR 1 · other 1

#112698 fix(gateway): resolve TUI state store home lazily · other → #102526
#112707 fix(tests): isolate the suite from the operator's live Hermes install · superseded by another PR → c712f06, #112692, #112698, #112799
#112799 fix(tui_gateway): resolve the launch state.db path at first use, not import time · PR volume cleanup → 7ee008a, 30b143c, #112692

Closed issues · 1

Closed#112692tui_gateway tests fail locally: server.py pins HERMES_HOME at import time, before the conftest sandbox

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.40: 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: #113224
Closed issues: 1
Attempts: 3 PRs closed without merging
Fix link checked: 17 Sep 2026

For your agent

The same facts, typed.

cluster/112692.json
cluster/112692.md