Dashboard Shows Sessions But No Messages After v0.18.0 Update
Bug tracker — July 8, 2026. Hermes bug #60868 is a frontend regression where the web dashboard at localhost:9119 lists session titles correctly but renders blank conversation areas. The data is intact, the API works, and the frontend simply never calls the messages endpoint.
The Failure in One Sentence
The dashboard frontend renders session titles in the sidebar, but when you click into any session, the conversation area is blank. The session data is intact — the CLI can read and continue sessions normally — but the frontend does not call the messages API endpoint that would populate the conversation view.
API-Level Diagnosis Confirms Frontend Bug
| API Endpoint | Status | Returns |
|---|---|---|
/api/sessions | Working | Session metadata correctly |
/api/sessions/{id} | Working | Session detail (metadata only, no messages) |
/api/sessions/{id}/messages | Working — returns 200 with full message history | Full message history intact |
The diagnosis is precise: the messages API endpoint exists, is reachable, and returns correct data. The dashboard frontend in v0.18.0 simply does not call it when a session is selected. The data is there. The frontend is not asking for it.
What the User Sees vs What Is Actually Happening
| What the User Sees | What Is Actually True |
|---|---|
| Blank conversation area | Full message history exists and is retrievable |
| Apparent data loss | CLI commands like hermes sessions list and hermes --continue work normally |
| Broken dashboard | Only the frontend message-loading path is broken; sessions and metadata load correctly |
This is a user-experience regression with an outsized trust impact. A blank conversation area after an update looks like data loss. It is not — but the user cannot tell the difference between a frontend bug and lost work without dropping to the CLI.
The 3rd Dashboard/Web-UI Regression
| Issue | Date | Failure Mode |
|---|---|---|
| #57790 | Jul 3 | Dashboard web down after hermes update, python command missing |
| #57786 | Jul 3 | Dashboard web stopped working — disk space exhaustion from logs |
| #60868 | Jul 8 | Dashboard renders blank conversations — frontend not calling messages API |
Three distinct dashboard failures across two different root causes (infrastructure and frontend) in under a week. For users evaluating whether to trust a local agent platform with their daily workflow, dashboard reliability is not optional — it is the primary interface for reviewing and continuing past work.
Why This Matters for Review-Site Readers
- Dashboard is the primary UX surface for session history. When the dashboard breaks, users lose the ability to review, search, and continue past conversations through the web interface. The CLI workaround exists but is not the experience users signed up for.
- The failure looks like data loss. A blank conversation view after an update is indistinguishable from lost work to a non-technical user. The trust damage is real even though the data is intact.
- A fix PR is already open (#60878). The bug is diagnosed and a fix is in progress — but the fact that a frontend regression this visible shipped in a release is itself a quality-signal data point for comparison shoppers.
Case Summary
- Source: GitHub issue #60868
- Opened: Jul 8, 2026
- Labels: P2, bug, comp/dashboard, type/bug
- OS: Linux Mint 22.3
- Reporter: @ddragon64
- Evidence: 5 debug logs provided, PR #60878 already linked
Source URL: https://github.com/NousResearch/hermes-agent/issues/60868