Hermes Console

Community

Read-only local dashboard for monitoring your Hermes setup. Runtime overview, session history, cron status, skills browser, memory visibility, and usage stats — all from local disk, no cloud.

Hermes Console is a local-first dashboard that reads directly from your ~/.hermes directory. It's intentionally read-only — no chat client, no terminal, just a clean view into what Hermes is doing. Perfect for monitoring without accidentally changing anything.

Features

  • Read-only monitoring
  • Runtime overview
  • Session history browser
  • Cron status and schedules
  • Skills browser
  • Memory visibility
  • Token usage estimates
  • No cloud dependency

Why this tool matters

The philosophy is visibility without control. You get gateway health, connected platforms, session history, cron schedules, skills, and memory — but no write operations. This makes it safe to use while debugging without worrying about side effects.

It reads from ~/.hermes by default with no external services, no auth overhead, and no cloud dependency. Everything stays local.

Useful for operators who want to see what's going on without switching between multiple terminal windows or messaging surfaces.

Best use cases

Monitor Hermes health and status at a glance
Browse session history across agents and platforms
Check cron job status and upcoming schedules
Identify memory pressure warnings before they become problems
Review skill configurations and dependencies
View on GitHub →

FAQ

Can I chat with Hermes through Hermes Console?

No. It's intentionally read-only. Use the TUI, messaging platforms, or other web UIs for chat.

Does it support multiple Hermes agents?

Multi-agent support is planned but not yet implemented. Currently it reads from a single ~/.hermes directory.

Do I need to expose ports or configure authentication?

No. It's designed for local use and reads directly from disk. No network exposure needed.

Related Resources