Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Official Documentation

21.1. Official Documentation — The Authoritative Sources

The main repository

github.com/NousResearch/hermes-agent

This is where the actual source code lives, along with the install script (chapter 2.1), the complete set of default skills (chapter 10), the changelog, and the full issue/PR history — the right source to “verify the source” before installing or reporting a bug, instead of trusting a third-party blog that may already be outdated.

The full documentation site

hermes-agent.nousresearch.com/docs

All 20 chapters in this handbook (from VPS and Installation to the Improvement Loop) originate here, directly or indirectly — when a technical detail needs re-verification (configuration syntax, the exact tool name, a default value), this is the first place to look, before any other source.

The User Stories pages — real stories, not marketing

hermes-agent.nousresearch.com/docs/user-stories

A collection of real user experiences, including the valuable “failed, then rebuilt it myself” stories — for example, one user recounts writing their own three-layer “memory kernel” (L1 Hindsight, L2 Graphiti, L3 MemPalace) after three failed attempts with the built-in memory, illustrating exactly the limit described in chapter 9.6 (when the built-in memory is not enough and you need to move to an external memory provider).

Notes

  • When a community guide (21.2, 21.4) conflicts with the official docs, always trust the official docs — the community writes faster than the project itself can update its documentation, and easily goes stale with each release.
  • Before reporting a bug or opening an issue, check the changelog in the main repository — many “bugs” are actually deliberate behavior changes between versions (like the mandatory dashboard authentication rule described in chapter 2.3).
  • User Stories are a good source of real-world application ideas before you start fumbling your way from scratch — many good patterns (a personal memory kernel, cost-saving workflows) have already been tried and shared by others.