Cairn

Dashboard/TUI xterm.js rendering and scrollback bugs

NousResearch/hermes-agent · cluster 53641 · dashboard

Data as of

2 open items. Fix attempted, not merged.

The short answer

2open issues
0open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 0 PRs.

A cluster of bugs and fixes around xterm.js embedded chat in the dashboard and TUI, covering invisible or clipped text in long sessions, scrollback drift, WebGL black rows on load, and related UI rendering issues.

Open issues2

  • Issue#63384[Bug]: Text becoming invisible on long sessions
  • Issue#64744[TUI] Dashboard embedded xterm.js chat: streaming output text gets clipped/hidden until next interaction

Open PRs0

No open pull requests.

5 PRs closed without merging

From the close comments: superseded by another PR 2 · duplicate 1 · other 2

  • #63910 fix(web): make default foreground color visible (0% -> 100% opacity) · other → #63384
  • #64967 fix(tui/dashboard): use proportional drain for sticky-follow in xterm.js (#64744) · superseded by another PR → #64969, #64744
  • #64969 fix(tui): use proportional drain for xterm.js sticky-follow streaming (#64744) · duplicate → #64967, #64744
  • #64997 fix(dashboard): slash completion double-slash, copy button overlap, WebGL black rows on load · superseded by another PR → #66217
  • #66217 fix(dashboard): slash completion double-slash, copy button overlap, WebGL black rows on load · other
Closed issues · 1
  • Closed#53641Dashboard chat: new input/output invisible in long sessions — inline-mode cursor/scrollback drift (scales with transcript size)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.20: 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
dashboard
Closed issues
1
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/53641.json
cluster/53641.md