4d3815d7c2
A multiplexed gateway connects each served profile's adapter inside _profile_runtime_scope(<profile home>). The receive loop an adapter starts while connecting inherits that home override, so every final reply the bot sends is recorded from it. The ledger resolved its path through get_hermes_home(), which follows the override, and the rows landed in profiles/<name>/state.db. The boot sweep (sweep_recoverable) and the boot flood-timer arming (pending_retries) run in the launch context and open the launch state.db, so they never saw those rows. A served bot's reply cut off by a crash or SIGKILL between finalize and platform ACK was never redelivered, a flood-refused reply that spanned a restart was never retried, and resume_pending was not cleared for a session whose answer sat in the ledger. The ledger is meant to be one shared store: the boot sweep already scopes rows by (platform, adapter_profile), and the profile purge terminalizes rows in the shared store. _db_path now resolves from get_process_hermes_home(), as the gateway's other process-level files do (gateway.status). It deliberately skips the get_hermes_home() fallback that lifecycle_ledger uses when HERMES_HOME is unset: a default gateway started in the foreground has no HERMES_HOME, and that fallback would follow the override again. Rows an earlier build already wrote to a profile's state.db stay where they are.
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.