ec78ae2211
The persisted <available_skills> index is reused byte-for-byte across turns so the provider prefix cache stays warm (#104414). A skill that lands after the prompt was built (hub install, skill_manage from another session, org sync, curator) therefore never reached the index the model actually routes on until compaction rebuilt the prompt: skills_list is live, but the prompt tells the model to scan the index, not to call it. cloudflare-os#267 found the same fault in their chat-cached catalog ("a catalog states what a session can reach now, which is not a fact a chat can hold"). Hermes' idiom for stored-prompt drift is a one-shot note behind the cached prefix, not a rebuild, so agent/skills_index_delta.py stages the delta on the same per-turn user-message channel the surface-switch note rides: the added skills' own index lines (name + description, the routing signal), the removed names, cumulative against the stored prompt and re-staged only when the delta changes (read back from the api_content sidecar, so the gateway's fresh agent per turn does not stack copies). An undone delta retires the stale note once. The current index comes from the same cached builder the prompt did, so an unchanged turn costs one LRU hit.
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.