# Hermes-Wiki: a source-verified architecture wiki for the Hermes agent

> A documentation repository, not an agent. It maps the internals of Nous Research's Hermes agent across 46 concept pages and 50 changelogs, and it is the only thing in this repository that ships.

**cclank/Hermes-Wiki** — Hermes agent + LLM Wiki + 源代码 完成 Hermes agent  wiki 

- Repository: https://github.com/cclank/Hermes-Wiki
- Stars: 656 · Forks: 73
- Language: Unknown
- License: not declared
- Published: 2026-09-10 · Updated: 2026-09-10 · Language: en
- Canonical page: https://hysenlabs.com/projects/cclank-hermes-wiki

## What Hermes-Wiki actually is, and who it is written for

This repository is a knowledge base about another repository. Its README opens by describing itself as deep architecture documentation based on the source of Nous Research's Hermes agent, and it claims every page has been verified line by line against that source. The content lives in concepts/, changelog/, entities/ and a handful of top-level files including index.md, log.md and SCHEMA.md.

The audience is narrow and identifiable. If you are patching the agent loop, adding a provider plugin, or deciding whether the memory design will survive your workload, this is the layer you want. If you are an operator who just wants an assistant that answers questions, nothing here runs. There is no server, no package manifest, no binary. The README's own badges count pages and changelogs, not downloads, which tells you what kind of artifact this is.

The scope claim is the interesting part. Documentation that tracks an upstream project closely enough to cite commit hashes is expensive to maintain, and the README leans on that cost as its selling point.

## How the wiki is organised: concepts, entities and a dated changelog

The concepts directory is grouped by subsystem rather than by user task. Core architecture covers the agent loop and prompt assembly, the tool registry, model-tools dispatch, toolsets and the provider transport abstraction. A second cluster covers memory and sessions: a three-layer memory stack described as MemoryStore, MemoryManager and MemoryProvider, FTS5-backed session search, context compression, and the skills system. A third covers tools and capabilities, including browser automation, web search backends, the execute_code sandbox, voice mode, context references such as @file and @diff, fuzzy matching, large tool result handling, LSP diagnostics and i18n.

The remaining groups are performance, security, multi-agent and platform work. Multi-agent is documented as five runtime mechanisms, one of which is a persistent Kanban board backed by SQLite in WAL mode with heartbeats and circuit breaking. Platform coverage includes a messaging gateway described as spanning 22 platforms, seven terminal backends, a local proxy that exposes an OAuth-backed provider as an OpenAI-compatible endpoint, a hook system, a YAML skin engine, git worktree isolation and a cron scheduler.

The changelog directory holds 50 entries in reverse chronological order, and the newest one is unusually detailed. It records a single-day sync of 179 commits moving hermes-agent from 5a53e0f0 to 87ab373, with a breakdown by type and a file-level diffstat. Entries at that granularity are closer to release archaeology than to documentation, but they are the part of the repository most likely to stay accurate, because a changelog entry describes a fixed range of commits rather than a moving subsystem.

## Reading it locally and finding the page you need

There are no install steps in the README, because there is nothing to install. The repository is Markdown plus a schema file, so the practical first move is to clone it and read it with whatever Markdown viewer you already use. The README shows an Obsidian badge, which is a hint about the intended editing environment rather than a requirement.

```bash
git clone https://github.com/cclank/Hermes-Wiki.git
cd Hermes-Wiki
ls concepts/ | head
```

The listing should return the concept pages named in the README, such as agent-loop-and-prompt-assembly.md and tool-registry-architecture.md. From there, index.md is the entry point the README points to for the full changelog list, and SCHEMA.md describes how pages are structured. If you are checking a claim against upstream, the version badge in the README gives you the commit to compare against, and the newest changelog entry names both the old and new hashes for its range.

One caveat about paths: the README links concept pages with relative paths like concepts/agent-loop-and-prompt-assembly.md, so the links resolve only when you are reading the repository as a checkout or on a host that renders relative Markdown links. Open a single file in isolation and the cross-references between subsystems will not work.

## The verification claim is the whole product, and it has a shelf life

Everything in this repository rests on one promise: pages are verified against the source. That promise is also its main weakness. The README pins a specific version and commit, v0.17.0 at 87ab373, and the newest changelog entry is dated 2026-06-21. The last push to the repository was on 2026-06-21 as well. A wiki that documents internals at commit granularity starts drifting the moment upstream moves, and nothing in the repository layout suggests an automated check that would catch a stale page.

There is a second, subtler failure mode. The newest changelog entry is written at a level of detail that includes file paths and line ranges for individual fixes, such as a decay function in agent/context_compressor.py and a rollback path in hermes_cli/goals.py. That precision is useful when it is right and actively misleading when upstream refactors the file. A reader who trusts a line range without checking the commit will get a confident answer about code that no longer exists in that shape.

The honest framing is that this is a snapshot with a timestamp, not a living reference. Treat the version badge as a precondition for every page, not as decoration.

## How it compares with generated API docs and with the upstream repository

The obvious alternative is reading the Hermes agent source directly, and for a single question that is often faster. The wiki's advantage is cross-cutting: a question like how a tool result becomes a prompt token touches the tool registry, the dispatch layer, the prompt builder and the compression logic, and the wiki has a page for each with links between them. Source reading gives you ground truth with no drift risk; the wiki gives you a map with a fixed expiry date.

A second alternative is generated documentation from docstrings or type signatures. That approach stays current automatically but captures interfaces rather than intent. It will tell you that a function exists and what it accepts. It will not tell you why the memory system uses a frozen snapshot, which is the kind of design rationale the memory and prompt-caching pages appear to be built around. The trade is maintenance cost against explanatory depth, and this repository has chosen the expensive side of that trade.

A third option, for operators rather than contributors, is simply not using either and relying on the agent's own behaviour. That is reasonable until something breaks in a way the logs do not explain.

## Licence, maintenance cost and what upgrading involves

The README carries an MIT badge, and the repository has no separate licence file listed among its top-level entries. MIT is permissive, so quoting pages or vendoring them into internal documentation is broadly uncomplicated, but the badge is the only licence signal available here and a badge is not a licence text. If you need certainty for a redistribution or a compliance review, that is a question for your own counsel and for the upstream project's licence file, not for this README.

Maintenance cost falls on whoever keeps the wiki aligned with upstream. The 2026-06-21 entry shows what one sync costs when upstream lands 179 commits in a day: a full changelog page with a type breakdown, a diffstat and file-level notes on the notable fixes. Reproducing that per release is manual work, and the repository shows no tooling that would generate it.

Upgrading your copy is a git pull, which is trivial. The real cost is re-verifying the pages you depend on against the commit you actually run, because a pulled wiki and a pinned agent version can disagree silently.

## Conclusion

Adopt Hermes-Wiki if you are modifying the Hermes agent itself or evaluating its design, and you want page-level pointers into agent-loop, tool-registry and memory internals instead of reading the source cold. Do not adopt it if you want a runnable agent, a hosted service or a user manual; it contains no installable artifact and no end-user instructions. Before relying on any page, check the version badge against your checkout, since the wiki pins v0.17.0 at commit 87ab373 and the newest changelog entry is dated 2026-06-21.

## FAQ

### Is Hermes-Wiki the Hermes agent itself, or documentation about it?

It is documentation. The README describes it as deep architecture documentation based on the source of Nous Research's Hermes agent, and the repository contains Markdown concept pages, changelogs and a schema file rather than runnable code.

### How do I install Hermes-Wiki?

There is no install step because there is no software to install. Clone the repository and read the Markdown files, starting from index.md and the concepts directory; the README shows an Obsidian badge, which reflects the intended editing environment rather than a requirement.

### Which version of the Hermes agent does Hermes-Wiki document?

The README's version badge pins v0.17.0 at commit 87ab373, and the newest changelog entry, dated 2026-06-21, records a sync from 5a53e0f0 to 87ab373. Pages describe that state of the source, so a newer checkout may not match.

### What licence does Hermes-Wiki use?

The README carries an MIT badge. No separate licence file appears among the top-level repository entries, so the badge is the only licence signal in the repository.

## Sources

- [cclank/Hermes-Wiki on GitHub](https://github.com/cclank/Hermes-Wiki)
- [Issues](https://github.com/cclank/Hermes-Wiki/issues)
- [README](https://github.com/cclank/Hermes-Wiki/blob/master/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/cclank-hermes-wiki