453b1dec2b
bot_relay.deliver has two live-owner branches: the in-process prompt.submit handoff (#100523) and the sibling-process mailbox handoff (#113753). Both answered the sender with a receipt sentence — "Delivered into / Queued for @x's open Bot Chat; the reply will appear there" — so a bot on another machine never received the target's answer whenever the target's Bot Chat happened to be open. The owner's poller already settles a receipt carrying the reply, and local DMs wait on it (bot_mode_dm._wait_live_dm); the relay just never read it. Owner-first now: a live owner that advertises a mailbox — this process or a sibling — gets the DM through it, and the handler waits on the receipt on the local lane's budget: the reply comes back (a bare silence marker as ""), a failed or cancelled turn as the typed 5092 refusal, and a DM still unanswered at the budget is reported queued there with "do not resend". prompt.submit stays as the fallback for a live session with no mailbox. Fixes #115316 (cherry picked from commit 1f76e8f39be55ec63d7833da765ad5427a01e090) Rebuilt onto main as one commit after #116903/#116968/#117055 landed: relay tests guard both child seams; the cross-connection docs bullets are deduplicated. Co-authored-by: teknium1 <127238744+teknium1@users.noreply.github.com>
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.