Fleet telemetry (14d, v0.21.5) shows the builtin store returning success=False on 34-47% of add/replace/remove calls. Live `hermes chat -q` runs against origin/main reproduced the dominant causes: - Drift guard refused every replace/remove/batch on a file whose only difference from the tool's own layout was whitespace (blank lines around the delimiter, an empty entry). Parsing only strips whitespace, so flushing such a file loses nothing; the round-trip signal could not protect any content and turned the store read-only until hand-fixed (#107270). The guard now fires only on the signal that can actually lose foreign text: one entry larger than the whole store's limit. - An over-budget add/replace/batch said "would exceed the limit" but not by how much, so models retried with consolidations that were still too big. Every over-budget message now states the exact chars to free and points at the one-batch fix. - An old_text that matched nothing (paraphrased, stale after a concurrent write, or several entries glued with the delimiter) returned no hint on the batch path. Zero-match errors now carry `closest_entries` (top word overlap) on both paths, and flag a delimiter-spanning old_text. - A batch replace missing its own `content` now says to set it on the operation object. Fixes #107270. Same diagnosis as #107278 (@KoNit-K) and #61612 (@webtecnica), which normalized the round-trip comparison instead of dropping it.
Website
This website is built using Docusaurus, a modern static website generator.
Reading the docs on GitHub? The Markdown under
docs/is authored for the rendered site at https://hermes-agent.nousresearch.com/docs/. Cross-page links are relative Markdown paths, so they follow through on GitHub's file viewer too. Every page on the site has an Edit this page link that opens the source file here.
Authoring links in docs/
- Link to another page with a relative Markdown path, anchors included:
[Profiles](../user-guide/profiles.md),[Bundles](../user-guide/features/skills.md#skill-bundles). Docusaurus turns the file path into the page route; GitHub follows the same path. Site routes (/user-guide/profiles,/docs/user-guide/profiles) only work on the rendered site — GitHub resolves them as repository paths and 404s, and the/docs/form also emits/docs/zh-Hans/docs/...404s in the zh-Hans build becausebaseUrlis already/docs/. python3 website/scripts/check_doc_links.pyfails on any route-style link in hand-authored pages (EN and the zh-Hans mirror);--fixrewrites them. It runs in theDocs Site Checksworkflow. Generated pages (user-guide/skills/{bundled,optional},reference/*skills-catalog.md) are produced byscripts/generate-skill-docs.py, which emits the same relative form.- Pin
{#anchor}on cross-linked headings so the zh-Hans mirror keeps the same id.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.