hermesd CLI
hermesd shows Hermes Agent gateway, sessions, token spend, cron jobs and logs in one terminal, without writing to its state.
- 122 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads Hermes Agent session databases, logs and profile configs, so provider and channel names may appear in the output.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/hermesdDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads Hermes Agent session databases, logs and profile configs, so provider and channel names may appear in the output.
This is third-party code. Review the repository files before installing.
What it does
hermesd is a terminal dashboard that reads the `~/.hermes/` directory and refreshes 13 live panels: gateway and platform state, sessions, tokens and cost, tools, cron, skills, logs, providers and MCP servers. It needs no API keys or outside requests. The program is read-only and redacts secrets in its output. `hermesd --snapshot` prints a JSON snapshot for scripts. Linux and macOS are supported, with Python 3.11 or newer.
Who it is for. Hermes Agent owners running a gateway, several profiles and cron jobs who are tired of stitching the picture together from five commands.
Good fit when
- The Hermes gateway serves Telegram and Discord and you want a quick check that platforms are connected.
- Token spend jumped and you want per-model and per-session usage for 24 hours and 7 days.
- A nightly cron job may have failed and opening the log feels like too much.
- A monitoring script pulls a JSON state snapshot through `hermesd --snapshot`.
Not a fit when
- The agent is not Hermes: the panels read only the `~/.hermes/` layout.
- You need to control the agent rather than watch it: hermesd starts and changes nothing.
- The host runs Windows: only Linux and macOS are stated.
Example request
Run hermesd and tell me whether every gateway platform is connected and which cron jobs failed in the last day.Limitations
Some panels depend on records produced by a specific Hermes Agent version, and older schemas fall back to simpler views. The dashboard reads session databases, logs and profile configs, so JSON snapshots listing providers and channels should not be posted publicly. Secret redaction is described in the README, but only your own review of the output before sharing gives a full guarantee. Installation needs Python 3.11 or newer and Windows is not stated as supported. On older agent versions some panels stay empty because the needed tables and files do not exist yet.
How to disable. Quit with the exit key or Ctrl+C and remove the package with `pip uninstall hermesd` or `uv tool uninstall hermesd`. hermesd does not change data in `~/.hermes/`.
FAQ
Does it need API keys?
No. hermesd reads local files in `~/.hermes/` and calls no outside services. To check the gateway it may connect to the agent's local socket.
How do I point it at another Hermes home?
Pass the path with `--hermes-home PATH`. The default is `~/.hermes/`.
Can I get data for a script?
Yes, `hermesd --snapshot` prints JSON. Read the compatibility notes before upgrading, because some fields were renamed.
Does hermesd change agent data?
No. The program is read-only and writes nothing to `~/.hermes/`.
How do I upgrade?
Install the newer version with the same manager, `pip` or `uv`. Read the JSON snapshot compatibility notes before upgrading.
Discussion
No questions or reviews yet.
Related
CLI toolsA Hermes Agent skill and a standalone Linux watchdog that detects failures, diagnoses causes and restarts allow-listed services.
Telegram Dashboard for Hermes
hermes-agent-telegram-dashboard
A Hermes Agent plugin: agent state in one pinned Telegram message that is edited on a schedule. No Mini App and no model calls
Native macOS terminal with an MCP server and CLI: agents see panes, commands and output, and you grant permissions in one window
A local dashboard for Claude Code and Codex sessions: who is working, who waits for you, plus a 3D aquarium and Stream Deck
An MCP server built into the Harness terminal for macOS: agents read sessions and panes, and input is enabled by a separate flag
herdr-agent-usage (senna-lang)
herdr-agent-usage
A Herdr plugin with a limits pane: context fill, prompt cache and remaining subscription allowance for each agent.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| hermesd (this card) | no | 122 | |
| Telegram Dashboard for Hermes | no | 7 | shows Hermes state in Telegram; hermesd renders it in a terminal and goes deeper into gateway, cron and providers |
| Claude Code Agent Monitor | no | 1,180 | watches Claude Code sessions; hermesd reads the directory of a different agent, Hermes |
README in short
Install it separately so hermesd dependencies do not alter the agent's own environment. Digits switch panels and `j` and `k` scroll long views.