hermes - 💡(How to fix) Fix [Bug]: Web Dashboard: Session resume doesn't show full conversation history [1 pull requests]

Bug Description

When resuming a session in the web dashboard, the full conversation history is not accessible. The session loads and shows recent messages, but scrolling up to reach earlier messages is practically impossible — the xterm.js wheel scroll step is too small (~2 lines per tick), making it take ~255 individual scroll actions to reach the top of a 509-line history.

Steps to Reproduce

1. Start a long session via hermes chat with many tool calls (200+ messages)
2. End the session
3. Open the web dashboard (port 9120)
4. Click to resume the session
5. Attempt to scroll up to see earlier messages in the conversation

Expected Behavior

All conversation history should be visible and navigable after resuming a session in the web dashboard — either via smooth scrolling or keyboard shortcuts to jump to the top/bottom of the history.

Actual Behavior

The session resumes and shows only the most recent messages. Scrolling up requires ~255 individual mouse wheel ticks to traverse ~509 lines of history at ~2 lines/tick (ChatPage.tsx: Math.round(Math.abs(delta) / 50)). There are no keyboard shortcuts (e.g. Ctrl+Home/End) to jump to the start. The full history is effectively unreachable in practice.

Investigation confirmed:

• state.db: all 203 messages stored correctly
• tui_gateway/server.py → _history_to_messages: filters to ~144 messages
• ui-tui/dist/entry.js → toTranscriptMessages: collapses to ~62 rendered items
• MAX_HISTORY = 800 — not the bottleneck (62 << 800)
• xterm.js scrollback: 5000 — not the bottleneck (~544 lines total)
• Root cause: wheel handler delta/50 ≈ 2 lines/tick

Affected Component

Other

Messaging Platform (if gateway-related)

N/A (CLI only)

Debug Report

Report      https://paste.rs/bBEac
agent.log   https://paste.rs/yDS6D
gateway.log https://paste.rs/AjSXg

Operating System

Ubuntu 24.04.4 LTS

Python Version

3.11.15

Hermes Version

0.14.0

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR