03f545ebcf
Two install routes refused a catalog memory provider that config already names (memory.provider), so the install could never succeed and was retried on every agent start / every click — the hindsight (91%) and mnemosyne (87%) failed rows in hermes.extension.install.count. 1. Agent init (`recover_at_startup`) installs the configured provider through the consent gate. Under the classic CLI that gate's input() runs on the agent-build thread behind prompt_toolkit, so the turn hangs on "Initializing agent..." forever; with no terminal (Desktop, gateway, `chat -q`) it is refused — "Install declined: dependency install skipped (non-interactive)" — and recorded failed on every process start. Agent init now never asks: a provider that shipped in core installs with its built-in's consent (security.allow_lazy_installs still gates it), any other catalog provider is not attempted and the user is told the one command that installs it. 2. The dashboard/Desktop Install click (`dashboard_install_plugin`) on a plugin memory.provider already selects hits the publication veto that is meant for replacing an active plugin, so it is refused every time while the same plugin unselected installs and enables. The click now carries the consent the fresh-install enable already acts on; a forced reinstall keeps the veto.
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.