0761031767
* fix(plugins): portable MCP servers get a readable name so tool names fit the 64-char cap A portable plugin's MCP server was named `<skill_namespace>__<server>`, i.e. `agent-plugin-<slug>-<sha8>__<server>`. That prefix is right for plugin-data and skill names (collision-free without coordination, and persisted on disk) but it costs ~40 chars of every `mcp__<server>__<tool>` name. Providers cap function names at 64, so the registry clamped every tool of the NVIDIA plugin to a hash-suffixed stub with the verb cut off: `mcp__agent_plugin_hermes_nvidia_72eb26b1__nvidia_app__n_3fa9c2d1`. Server names only need to be unique among loaded portable servers, and the loader already refuses a clash. `portable_mcp_server_name(key, server)` = `<plugin-slug>__<server>`, collapsed to `<plugin-slug>` when the two match (the one-server package). The loader and the desktop card's server rows both call it (the card recomputed the f-string on its own before). Skill and plugin-data namespaces are unchanged; nothing persisted refers to the server name, so no migration. Tests: the existing portable-load test now pins the relationship (server name = plugin slug + server; a long vendor tool name reaches the wire unclamped), and a new test covers the clash the digest used to hide: two enabled packages folding to one slug, second server skipped, first served. Both red on main. Docs: developer-guide/plugins/index.md. * fix(plugins): a portable MCP server is named what its mcp.json calls it, nothing prepended Drop the plugin segment too. A user's own config.yaml server named `nvidia-app` yields `mcp__nvidia_app__<tool>`; a portable plugin's server of the same name now yields the same. Duplicates are refused at load (config.yaml first, then first-loaded plugin) with a warning naming both owners. Spike, isolated HERMES_HOME, real session: a portable plugin with server `acme-tools` and tool `acme_client_get_driver_status_report` registers as `mcp__acme_tools__acme_client_get_driver_status_report`; the model found it by tool_search, called it, and reported that exact name. Same plugin on main: `mcp__agent_plugin_acme_tools_88e7456f__acme_tools__acme_153862de`.
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.