nesquena/hermes-webui

WebUI sidebar shows session count badge but session list is empty

Open

#6,624 opened on Jul 30, 2026

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Python (2,386 forks)github user discovery
bugcli-parityhelp wantedsessionsprint-candidate

Repository metrics

Stars
 (17,368 stars)
PR merge metrics
 (Avg merge 14h 31m) (314 merged PRs in 30d)

Description

Bug description

The WebUI session sidebar shows a count badge (e.g., "(10)") under the WebUI Sessions tab, but clicking into the tab shows no sessions listed. The count seems to come from the Hermes state.db CLI sessions cache, but the sidebar list doesn't render them.

Steps to reproduce

  1. Set up Hermes WebUI pointing to an existing Hermes Agent installation with state.db containing TUI/CLI sessions
  2. Open the WebUI sidebar
  3. Observe the session count badge (e.g., "(10)") under WebUI Sessions
  4. Click into the tab -- no sessions appear

Expected behavior

Either the badge should show an accurate count matching the listed sessions, or the list should populate with the sessions counted in the badge.

Environment

  • Host: Linux (containerized, single-user)
  • Hermes WebUI version: exp-v0.52.157
  • Sessions in state.db: ~450 (25 tui, 10 subagent, 1 telegram, rest cron)
  • Settings: show_cli_sessions=true, inflight_state_max_sessions=50, CLI_VISIBLE_SESSION_LIMIT=20

Contributor guide

Research direction
Investigate how the session count badge is computed from the state.db cache and how the sidebar session list is rendered. Look for mismatched filters, pagination, or cache layers between the two data sources.
Tech stack
javascriptpythonsqlite
Domain
full stackdatabase
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPythonSQLite
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75