9c4eecb53d
/initiate-setup is a prompt built-in in the /plan shape on the CLI, the TUI, the desktop app and the messaging gateway (/initiate_setup on Telegram). It sends one normal user turn: a fixed "[/initiate-setup]" header, the optional-skills initiate-setup SKILL.md read in place, and a JSON fact block with the SKILL.md key names (surface, tools_present, primary_profile, guest_free_tier, plus the host_facts.py collect() output at top level). Each surface resolves the tools present without a live agent, the same way /tools does, and builds under the session's profile scope. The first-contact note no longer carries the profile-build directive (memory tool, web lookups). With onboarding.profile_build "ask" it asks for a short intro that ends with one line offering /initiate-setup, latched once as before. The note is skipped when the first message is the rendered /initiate-setup prompt. The classic CLI now stages the same note. Placement: the gateway and CLI handlers live in gateway/slash_commands.py and hermes_cli/cli_chat_turn_mixin.py because run_inbound.py and cli_commands_mixin.py are already over the 2000-line gate. Gateway dispatch maps "-" to "_" in the _hm_cmd_ lookup. The prompt builder now runs off the event loop (asyncio.to_thread), because this builder reads files and probes the host.
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.