27e30a28d5
Every gateway's `default` profile is `@hermes`, so a remote default titled "CoS Bot" was unreachable by any bare form: `resolve_remote_target` matched handle/profile only, the prompt roster offered it as `@hermes` (which local resolution routes to THIS gateway's default), and the DM it sent arrived stamped `(@hermes)` so a reply hit the recipient's own default. - `tools/bot_relay.py`: `_target_aliases` adds the Bot Mode title's mention slugs; `resolve_remote_target` accepts them (exact handle/profile keeps precedence over a colliding title); `remote_target_forms` picks the shortest form no LOCAL profile and no other remote row answers to — bare handle, title slug, then `handle@connection` — independent of roster order; `qualify_sender_stamp` rewrites a relayed `Message from 🤖 … (@handle):` to that form. - `tools/bot_mode_probe.py::local_taken_forms` feeds the local handles and friendly-name slugs into the roster paragraph; `bot_mode_dm` lists ambiguous candidates with the same forms. - `tui_gateway/methods_bot_relay.py::bot_relay.deliver` re-stamps the sender before the transport branch (the recipient knows `from_connection`; the sender does not know its own Desktop id). Slim redo of #103767's Python half (@fangliquanflq): that PR always qualified every remote form with its connection id and reworked the Desktop mention Map; this keeps bare forms where they are unambiguous and leaves the Desktop picker untouched. Part of #103731 Salvages #103767 Co-authored-by: fangliquanflq <fangliquanflq@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.