TUI bundle staleness check and rebuild loop fixes

NousResearch/hermes-agent · cluster 25351 · gateway

Data as of

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

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #48561. 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.

These issues and PRs address incorrect bundle filename detection in the dashboard TUI staleness check, which caused infinite or blocking npm rebuild loops on every PTY spawn, including failures on read-only filesystems and behind reverse proxies. Related work includes switching the TUI bundle to esbuild and fixing off-event-loop argv handling.

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.

  • #48561 fix(dashboard): resolve chat TUI argv off event loop

    merged to main

    files: hermes_cli/web_server.py, scripts/release.py, tests/hermes_cli/test_web_server.py

2 PRs closed without merging

From the close comments: stale or abandoned 1 · superseded by another PR 1

  • #20951 fix(tui): correct hermes-ink bundle filename in staleness check · stale or abandoned
  • #26124 fix(dashboard): resolve chat TUI argv off event loop · superseded by another PR → #48561
Closed issues · 2
  • Closed#25351Dashboard chat silently breaks behind reverse proxies: _hermes_ink_bundle_stale() always returns True, triggering 15s blocking npm run build on every PTY spawn
  • Closed#30228Dashboard --tui fails on read-only /usr: ink-bundle.js / entry-exports.js filename mismatch causes infinite rebuild loop
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.44: 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
#48561
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
19 Jun 2026

For your agent

The same facts, typed.