3861f1da62
Desktop's web picker had no way to send one capability through the Nous Tool Gateway while the other used your own key. "Use for Search/Extract" on the Nous Subscription row wrote the row's vendor string (firecrawl) into web.<cap>_backend, which the runtime reads as BYOK Firecrawl: the gateway was never used, and the managed and BYOK rows lit up together. - The managed per-capability pick now stores `nous`; search/extract dispatch, the registry and the Firecrawl client resolve the route per capability (search: managed Perplexity, extract: managed Firecrawl). - A whole-toolset Nous pick clears stale per-capability pins (they outranked the new selection). - /api/tools/toolsets/web/config reports search_via_nous / extract_via_nous and each row's managed_nous_feature; the panel lights the right row, labels the route, and refetches after a pick instead of mirroring the vendor string. Fixes #100513. Builds on the approach in #100539 by @liuhao1024 and the self-healing pin clear from #122676 by @praggybuilds. Co-authored-by: liuhao1024 <sunsky.lau@gmail.com> Co-authored-by: Murphy (praggybuilds) <praggybuilds@users.noreply.github.com>
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.