Hermes dashboard
- 2 Devlogs
- 11 Total hours
It is really hard to visualize and mange agents such as Hermes and open claw, so i made a dashboard to visualize and mange these tasks
I finished building a local web dashboard that acts as a central control panel for my Hermes setup, making it possible to manage Ollama models, the Discord gateway, agent settings, system resources, maintenance tasks, and configuration files from a single interface instead of relying on terminal commands or manual file edits. The application launches through a simple startup script, runs a lightweight Python backend, and serves a browser-based UI that communicates with Hermes and Ollama through API calls.
What it does
It’s a dashboard for everything Hermies-related:
See status — Is Ollama running? Is the Discord bot online? Which model is active?
Start/stop things — Start Ollama + Discord gateway with one click, or restart them individually
Switch models — Pick which Ollama model Hermes uses, pull new ones, delete old ones
Control resources — Limit GPU/CPU so models don’t stutter your PC (presets like Stability/Balanced/Performance, or per-model sliders)
Configure Discord — Bot token, allowed users, start/stop the gateway
Tweak agent settings — Memory, reasoning, timeouts, display options
Run maintenance — Health checks, view logs, list skills/cron jobs, backup
So instead of typing hermes gateway start or editing config files by hand, you click buttons and fill in forms.
How it works
You open it — Double-click Open Hermies.vbs (or .bat). That starts a small Python server and opens your browser.
Backend — server.py listens on port 7580 and handles API requests. core.py does the real work: talks to Ollama, runs Hermes CLI commands, reads/writes config files in %LOCALAPPDATA%\hermes.
Frontend — index.html, styles.css, and app.js render the UI. When you click something (e.g. “Start Gateway”), JavaScript sends a request like POST /api/gateway/start, the server runs the matching function in core.py, and the result is shown in the dashboard.
Data flow — The panel doesn’t replace Hermes or Ollama. It sits on top of them: it edits config.yaml and .env, calls hermes commands, and talks to Ollama’s API. Your actual AI still runs through Hermes + Ollama; the website is just the remote control.
In short: local web app → Python backend → Hermes/Ollama/config files on your machine.
