Hermes Control Center

What Hermes Control Center does

Hermes Control Center treats chat as one panel among many. The main screen is an arrangeable dashboard of twelve widgets, covering system load, mission status, agent health, live logs, scheduled jobs, skills, MCP servers, model, token and cost analytics, recent sessions, insights and knowledge. Chat runs over the Hermes dashboard that is already running, with no API server and no gateway restart, and a cancel button is wired to Hermes' own turn interrupt.

Management pages cover skills, MCP servers, models with per-provider authentication state, scheduled tasks, knowledge and memory providers, integrations, logs and analytics, with write actions behind confirmations. A Telegram area shows the bot's configuration and every conversation that came through it. Workflows chain prompts, scheduled jobs and notes, run on demand or on a schedule, and keep the last five runs. A prompt library with placeholders, rule-based insights, a Ctrl or Cmd K command palette and English, German and Persian interfaces round it out. The README labels v1.0.0 as stable and says empty panels show an empty state rather than invented numbers.

Key features

• Twelve draggable, resizable dashboard widgets
• Chat over the existing Hermes dashboard with a real turn cancel
• Management pages for skills, MCP servers, models, scheduled tasks and logs
• Telegram area showing bot status and conversations
• Runnable workflows chaining prompts, scheduled jobs and notes
• Prompt library, rule-based insights and a command palette

When to use it

• Monitoring agent health, cost and token use at a glance
• Chaining prompts and scheduled jobs into a workflow that runs unattended
• Reading Telegram conversations with the bot from a browser

Who it is for: Hermes Agent operators who want a monitoring-style control room for their self-hosted agent.

How it fits with Hermes Agent

Built for Hermes Agent: it runs on top of the Hermes dashboard and manages its skills, MCP servers, models and scheduled tasks.

Note: The README says the package is not on npm yet, so it must be installed from a clone until the first release is published.

FAQ