2dcebe6471
Hermes and everything it launches (browser profiles, PTY probes, skill scripts, tempfile defaults in delegated code) wrote to the system temp dir, which is a RAM-backed tmpfs on most Linux hosts and containers and fills under agent load. - hermes_constants.get_scratch_dir(): HERMES_HOME/cache/scratch (0700), entries older than 72h pruned once per process / once per hour across processes. - apply_scratch_tmp_env(env) / export_scratch_tmp_env(): TMPDIR/TMP/TEMP point at the scratch dir when the user or OS has not set them; a value Hermes itself exported (== HERMES_SCRATCH_DIR) is re-derived for a re-homed process or a child served under another profile, so profiles never share scratch. - hermes_bootstrap runs the export on import (every entry point); hermes_cli.main re-runs it after --profile resolution; the subprocess HOME contract (apply_subprocess_home_env) and the routed-home rewrites in code_execution_env and served_profile_child_env apply it to child envs. - The runtime-environment prompt block names the scratch dir so the model stops reaching for the system temp dir by reflex; hermes doctor reports the dir, its size and whether a user TMPDIR overrides it.
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.