NousResearch/hermes-agent
TUI startup failure due to --expose-gc flag handling
Cluster 17187. Data as of
Nothing open on GitHub. Fix merged in #29998 on 21 May 2026. Check it covers your case.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #29998. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #29998. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the Hermes TUI fails because --expose-gc was incorrectly passed via NODE_OPTIONS, and related fix attempts to pass it as a direct Node.js CLI argument instead.
Open issues0
Open PRs0
Fixes on record
-
#29998 fix(tui): pass --expose-gc as node argv instead of NODE_OPTIONS
files:
hermes_cli/main.py,scripts/release.py
2 PRs closed without merging
From the close comments: merged via another change 1 · stale or abandoned 1
Closed issues · 1
- Closed#17187[Bug]: `hermes --tui` fails with `--expose-gc is not allowed in NODE_OPTIONS`
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.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
- #29998
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 21 May 2026