da2b64304b
Re-review of the trust-anchor follow-up: - Cron runs and Kanban workers no longer anchor trust. The cronjob tool lets the model pick a job's workdir, which becomes the run's session cwd, and kanban_create lets it pick a task workspace, which becomes the worker's launch dir and TERMINAL_CWD. Either one let an agent-cloned repo become trusted. Both now rely on lsp.trusted_workspaces only. - A repository at or above $HOME never anchors, not only one at $HOME exactly. - Operator roots are recorded only where a tool thread enters (enabled_for) and when the service is created. _trusted() is now a pure read. Before, it took _state_lock while two of its callers already held it, so a change in the roots could deadlock the LSP loop. - Client lookups go through _live_key(). A multi-root client that started while its root was untrusted is still found and released after the root becomes trusted, instead of being orphaned. - `hermes lsp status` stops listing roots that have since become trusted. The lint gate reads the cwd the same way the linter subprocess does. - The path-list parser returns None for a malformed value, and each key logs its own warning. The _node_modules_trees docstring no longer mentions Vue.
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.