What it does Hermes Web UI is the frontend and desktop wrapper for Hermes Agent. It gives you a single interface to manage AI chat sessions, configure bot integrations across eight platforms (Telegram, Discord, Slack, WhatsApp, Matrix, Feishu, WeChat, WeCom), schedule cron jobs, track token usage and costs, browse remote files, and manage models and profiles. It stores its own session database in SQLite, keeps Hermes history read-only, and can run as an Electron desktop app, an npm global install, or a Docker Compose stack.

The interesting bit The platform channel configuration is unusually thorough: per-platform credential management writes to ~/.hermes/.env, behavior settings go to ~/.hermes/config.yaml, and the UI detects configured vs. unconfigured status for each channel. That’s a lot of plumbing for what could have been a simple webhook form. The multi-agent group chat with @mention routing and automatic context compression when history bloats is also not a standard dashboard feature.

Key highlights

• Real-time chat streaming over Socket.IO with tool-call expansion and per-session token badges
• Profile-scoped everything: uploads, sessions, jobs, usage, memory, skills, providers, and model visibility are isolated per profile
• File browser works across local, Docker, SSH, and Singularity backends with upload/download/rename/move/delete
• Web Terminal via node-pty with multi-session support over WebSocket
• Desktop builds for macOS, Windows, Linux; Docker Compose with integrated Hermes Agent; or npm install -g hermes-web-ui

Caveats

• Default bootstrap credentials are admin / 123456; the README notes users are prompted to change these after login, but this is still a footgun for quick spin-ups
• Session search (Ctrl+K) only covers the Web UI’s local SQLite database; read-only Hermes history sessions are excluded, so you may need two searches to find something
• The README is truncated mid-variable-table, so some environment variable details are incomplete

Verdict Worth a look if you’re running Hermes Agent across multiple chat platforms and need centralized ops. Skip it if you just want a lightweight chat UI — this is a heavy operational dashboard with RBAC, cron scheduling, and multi-backend file management that assumes you’re already committed to the Hermes ecosystem.