toor
5e1003ceb7
The project shipped a black-and-white theme that was only half converted: the login page looked right, the message page was halfway, and the settings page had not been started. This finishes the move to the CYBER reference in prototype_reference/. Colors now come from a single token source (styles/variables.scss), where every semantic color is declared twice: once as OKLCH for the CSS, and once as an RGB triple so translucent variants can be built as rgba(var(--*-rgb), alpha). Cyan is the system itself, amber means the user has to intervene, green means the machine is working, and red only ever means something broke. The RGB triples are derived from the OKLCH values so the two declarations cannot drift apart. Pages adopt the .cy-* shell classes from the reference (view, panel, kpis, tabs, grid, table, field) instead of ad-hoc markup, which is what makes 19 of 26 views consistent. The remaining seven are deliberately bespoke: chat streams, the kanban board, the workflow canvas, the terminal, and the missing-agent screen. The chart palette and the kanban column colors move into single-source modules so they cannot drift either. A new guard test rejects raw hex colors, named colors, and literal RGB triples anywhere in the client source, with an explicit exemption list for the places that genuinely cannot read a CSS variable. The existing chat semantics spec keeps the chat chain honest. No behavior changes: no logic, no i18n keys, no data structures, and the /chat-run event contract is untouched.
hermes-ui
Self-hosted web dashboard for Hermes Agent — chat, session history, skills, MCP servers, model management, IM channels, file management, and usage analytics in one browser UI.
This project is under active rebuild. Feature work is being staged phase by phase; see
docs/phases/README.mdfor the current plan.
Prerequisites
hermes-ui runs as a plain Node.js server. It does not bundle a runtime.
- Node.js
>=23 - Python with
hermes-agentinstalled
Install hermes-agent, then either put hermes on your PATH or point HERMES_BIN at the
executable:
export HERMES_BIN=/path/to/hermes
If the CLI cannot be found, the UI shows an install hint instead of failing silently.
Getting Started
npm ci --ignore-scripts
npm run build
npm start
Then open http://localhost:8648 and log in with the default credentials printed on first start.
For development with hot reload:
npm run dev
The client runs on http://localhost:8649 and the Koa server on port 8647.
Layout
packages/client Vue 3 client: views, components, Pinia stores, i18n, API helpers
packages/server Koa API, Socket.IO chat runtime, SQLite stores, Hermes integration
packages/skills Built-in skills injected into the Hermes skills directory
tests Vitest unit/integration tests and Playwright browser tests
scripts Build and repository harness scripts
docs Architecture, harness docs, and the phased build plan
Docker
docker compose up -d
The image is based on nousresearch/hermes-agent, so Python and the Hermes CLI are already
present in the container.
Configuration
| Variable | Purpose |
|---|---|
HERMES_BIN |
Path to the hermes executable. Falls back to hermes on PATH. |
HERMES_HOME |
Hermes profile directory. Used to isolate profiles. |
HERMES_WEB_UI_HOME |
Web UI state directory. Defaults to ~/.hermes-web-ui. |
HERMES_WEBUI_STATE_DIR |
Alternate override for the Web UI state directory. |
PORT |
Server port. |
The HERMES_WEB_UI_* prefixes and the ~/.hermes-web-ui data directory are kept from the
0.6.x line on purpose, so existing deployments and data directories keep working.
Commands
| Command | Description |
|---|---|
npm run dev |
Run client and server with hot reload. |
npm run build |
Type-check and build client and server bundles. |
npm start |
Serve the production build. |
npm run test |
Run Vitest tests. |
npm run test:coverage |
Run Vitest with coverage. |
npm run test:e2e |
Run Playwright browser tests. |
npm run harness:check |
Validate repository docs, workflows, and package scripts. |
npm run openapi:generate |
Regenerate docs/openapi.json. |
License
BSL-1.1. See LICENSE.