hermes - 💡(How to fix) Fix [Bug]: Dashboard TUI scroll regression in v0.14.0 — long sessions truncated / missing history [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Bug Description

In Hermes Agent v0.14.0, the Dashboard TUI chat window fails to render the full history of long conversation sessions. Scrolling to the top of the transcript reveals that older messages are missing/truncated, effectively cutting off the beginning of the conversation history.

Steps to Reproduce

  1. Launch Hermes Agent v0.14.0 and open the Web Dashboard (hermes dashboard).
  2. Open a long conversation session (several hundred messages).
  3. Scroll up using PgUp or mouse wheel to view earlier messages.

Expected Behavior

The full conversation history should be accessible. Previous versions used virtual scrolling which handled large transcripts efficiently without DOM performance issues.

Actual Behavior

Messages at the beginning of the session are missing from the DOM. Scrolling up hits a hard limit where no more content is loaded or rendered.

Environment

  • Hermes Agent Version: v0.14.0
  • OS: Linux (Alibaba Cloud ECS)
  • Browser: Microsoft Edge (Chromium)
  • Node.js: v20.20.2
  • NPM: v10.8.2

Additional Context

This regression appears to have been introduced by commit afffb8d9a fix(dashboard): use browser scrollback for chat wheel. The change replaced the virtual scrolling mechanism with native browser scrolling to fix mouse wheel issues, but inadvertently broke the rendering of long session histories. The DOM likely truncates or fails to keep earlier nodes in memory, which virtual scrolling previously handled.

Please consider reverting to virtual scrolling or implementing a virtualized native scroll solution for v0.14.1.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING