b96e88b245
A staged replace/remove recorded only its old_text search string, and /memory approve re-ran that search against the file as it was at approval time. The background review stages every replace/remove it wants (#105921), so when the live agent updated the targeted entry in place and the new text still contained old_text, approving deleted or overwrote the newer entry the approver never saw, and the output said only "Approved 1 memory write(s)." - Both staging gates resolve each replace/remove, under the store lock, to the full entry it matches and record it as matched_entry. No match or an ambiguous match is refused at staging, as the direct write is. - Approval matches that entry exactly. If it changed since staging, the write is refused and the pending record is kept, as #96059 does for skills. - /memory approve lists removed entries next to overwritten ones, so a record staged before this change (no matched_entry, still replayed by old_text) never removes an entry silently. - /memory pending shows the full entry each staged replace/remove targets, not just its search string. (cherry picked from commit 28700fa750c9321ded48be77a76531b5809f5fea)
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.