Hermes Agent setup guide (V2) — fact-check and revision log
This page documents how the Hermes Agent setup guide (V2) was written and reviewed. The guide itself is at /guides/hermes-agent-setup-v2/. V2 supersedes the earlier drafts (the original setup guide and a MiniMax M3 comparison draft), both of which are kept in the /guides/ index for historical reference.
Sources used
Official Hermes Agent documentation
- Hermes Agent installation docs — hermes-agent.nousresearch.com/docs/getting-started/installation
- Hermes Agent quickstart docs — hermes-agent.nousresearch.com/docs/getting-started/quickstart
- Hermes CLI commands reference — hermes-agent.nousresearch.com/docs/reference/cli-commands
- Hermes configuration docs — hermes-agent.nousresearch.com/docs/user-guide/configuration
- Hermes providers docs — hermes-agent.nousresearch.com/docs/integrations/providers
- Hermes tools docs — hermes-agent.nousresearch.com/docs/user-guide/features/tools
- Hermes skills docs — hermes-agent.nousresearch.com/docs/user-guide/features/skills
- Hermes memory docs — hermes-agent.nousresearch.com/docs/user-guide/features/memory
- Hermes messaging docs — hermes-agent.nousresearch.com/docs/user-guide/messaging/
Source repo and installer checks
- NousResearch/hermes-agent GitHub repo — github.com/NousResearch/hermes-agent
- Linux/macOS installer script — raw.githubusercontent.com/.../scripts/install.sh (second source for the shell installer path)
- Windows installer script — raw.githubusercontent.com/.../scripts/install.ps1 (second source for the PowerShell installer path)
Live command checks
The commands below were checked against live --help output from a working Hermes install on July 10, 2026:
hermes --helphermes setup --helphermes model --helphermes tools --helphermes gateway --helphermes config --helphermes memory --helphermes skills --help
Claim audit
Verified against the official docs
- The Linux/macOS/WSL2/Termux installer is the curl-piped shell command. ✓ Confirmed in the installation docs.
- The native Windows installer is the PowerShell
iex (irm ...)command. ✓ Confirmed in the installation docs. hermes --versionprints version, install method, and local install path. ✓ Confirmed against--helpand a real run.hermes doctorruns a preflight health check. ✓ Confirmed in the user-guide configuration docs.hermes modelopens an interactive provider/model picker. ✓ Confirmed in the providers docs.hermes setup --portalis the one-shot Nous Portal path with OAuth login, model selection, and Tool Gateway opt-in. ✓ Confirmed in the providers docs and CLI help.- The toolsets model (file, terminal, web, browser, memory, skills, cronjob, computer-use, etc.) is documented. ✓ Confirmed in the tools docs.
- Memory has built-in storage and an external provider path via
hermes memory setup/status/off/reset. ✓ Confirmed in the memory docs. - Skills are reusable procedures managed via
hermes skills browse/search/install/list/config. ✓ Confirmed in the skills docs. - The gateway is configured and run via
hermes gateway setup/run/install/start/status/list. ✓ Confirmed in the messaging docs.
Claims that remain conditional by design
- Provider availability changes (a provider listed today may be removed next month). Kept as a general principle in the guide.
- Toolset claims are deliberately phrased as "Hermes can X when the toolset is enabled" rather than as universal claims.
- Custom OpenAI-compatible endpoints depend on the actual endpoint's behavior — the guide tells the reader to verify the endpoint outside Hermes first.
- Memory file paths are not pinned to a single location. The guide points at
hermes memory statusandhermes memory setupas the safe source of truth, avoiding any "all memory is always at X path" claim.
Revisions applied during review
V2 is the second review pass. Compared to the original setup guide and the MiniMax M3 comparison draft:
- Restructured the guide around the layer table (CLI/chat → provider/model → tools → memory/skills → gateway → cron/plugins/MCP) so failures can be attributed to one layer at a time.
- Added a dedicated command map early, with what each command actually does, what success looks like, and what to do on failure. The original guide buried commands in flow.
- Added the
hermes setup --portalshortcut as a first-class path for Nous Portal users, with the trade-off noted. - Added the "memory vs skills" disambiguation. Memory is for facts; skills are for procedures. The original draft conflated the two.
- Added the conditional phrasing rule for tool-dependent claims. "Hermes can inspect files" became "Hermes can inspect files when the file toolset is enabled and allowed in that platform."
- Added the verification checklist as a numbered table so the reader can prove each layer in order.
- Added the cost section with two habits (keep the main path boring; use
hermes insightsto review actual usage). - Removed two first-pass MiniMax M3 outputs that returned unified-diff/tool transcripts instead of articles (the new raw-output gate rejected them).
- Removed version-number and private-path claims that were specific to one machine.
Earlier drafts (kept for reference)
- Original setup guide — the first draft, before the layer table and command map were introduced.
- MiniMax M3 comparison draft — a parallel draft from the MiniMax M3 model, useful for comparing how the same prompt produced different structures. V2 absorbs the useful parts (e.g. the conditional phrasing for toolset claims) and discards the brittle ones (e.g. an unsupported "default path is OpenRouter" claim).
Last verified
July 10, 2026 against the official Hermes Agent documentation, the GitHub README, the installer scripts, and live CLI help from a working Hermes install. Re-check the current docs before following a command after an upgrade. The verification checklist in the guide is the same set of commands a reader can run to confirm their own install.