3ed40556ce
A `hermes -p B` child built from a process that loaded profile A's env (a gateway, the dashboard, the post-update fleet restart) started with A's `DISCORD_ALLOWED_CHANNELS`, `TELEGRAM_GROUP_ALLOWED_CHATS`, `GATEWAY_ALLOW_ALL_USERS`... and enforced them as its own: gates are not credentials (no secret scrub sees them), a unit-file `Environment=` or operator export is in no dotenv (no name-list strip sees them), and B's own `.env` rarely defines the key (its dotenv load never overwrites the inherited value). Observed as profile B's gateway rejecting every message in B's own channel after a per-profile restart issued from A (#113270). - `local_env_policy.is_profile_gate_env` / `strip_profile_gate_env`: gates matched by shape (`_ALLOWED_`, `_ALLOW_ALL_`, `_ALLOW_FROM`, `_ALLOW_BOTS`, `_IGNORED_CHANNELS`, ...), never `HERMES_*`, so a gate added to any adapter is covered without a second edit. - `strip_launch_profile_env` drops them on its existing routed-home branch: the seam `served_profile_child_env`, the kanban dispatcher, cron workers and the dashboard action env already funnel through (the dashboard site now calls it for its target). Same-home children keep an operator export. - `update_restart_recovery._child_environment(profile)`: the one site that bypassed every helper (bare `os.environ.copy()` relaunching EVERY profile) strips gates when the profile is not the one the updater runs as; the module stays stdlib-only at import time. Live: fresh-process `hermes_cli.update_restart_recovery --stdin` with three gates in the updater env — base hands all three to profile b's relaunch, fixed hands none and keeps them for the launch profile. Refs #113270; supersedes #113308 (@yashraj4, static key list + always-strip; this keeps same-profile children intact and covers the per-adapter gate set).
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.