7fe77f29a7
Deleting an idle scratch entry left two things behind. Headless browsers started by a lane's e2e run kept running for days with a "(deleted)" cwd (about 20 on one host; the process registry never knew them because they were grandchildren of a shell that had exited). Repos whose linked worktree lived in the entry kept a dangling registration until someone ran `git worktree prune` by hand (10 in one repo). The prune now lives in hermes_constants_scratch (hermes_constants keeps the entry point). Before an idle entry is removed, same-user processes whose cwd is inside it, or inside any scratch path that no longer exists, are TERMed then KILLed; the deleted-cwd sweep runs on every pass so orphans from earlier deletions are caught too. `.git` files found in the entry name their repo, which gets `git worktree prune` after the rmtree. cache/terminal used its own 72h fixed-age sweep; it now shares the 24h idle rule and the subtree check. `hermes doctor` warns about cache-root directories over 1 GiB that neither pruner covers, since finished campaign trees parked there sat for weeks (95 GB on one host). System-prompt scratch line updated to match.
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.