ff6b9f722d
`start()` asked "Install it now so the gateway starts on login?" with default Yes, then called `install()` which asked two more default-Yes questions; on a redirected stdin (`< /dev/null`, scripts, agent tool calls) all three answered themselves and a bare `start` wrote a Startup-folder login item, spawned the gateway, and start() spawned it a second time (#113977). - The persistence question is answered only explicitly: `HERMES_GATEWAY_INSTALL_START_ON_LOGIN` (which start() never consulted before) or a prompt on a real TTY. Without a TTY, or under `HERMES_NONINTERACTIVE=1`, the answer is No: the gateway starts, nothing persistent is written, and the explicit `hermes gateway install` command is printed. - Declining on a TTY also starts the gateway — the command is `start`; only persistence was declined. - A Yes hands `start_now=True, start_on_login=True` to install(), which spawns and reports (including the UAC hand-off), so start() no longer double-spawns and no longer prints the false "Gateway install did not complete in this process" after an install that was skipped by intent. - `install --no-start-on-login` without `--start-now` now hints `hermes gateway run` instead of the `hermes gateway start` that used to offer the very auto-start just declined. Supersedes #113981 (@KoNit-K), which flipped the first prompt's non-TTY default but left the env override, the hint text and the false warning in place.
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.