5cabfa5d13
Bot Mode room members each keep a hidden `Group: <roomId> · <thread>` plumbing session that grows with every drive. When it bloats the member degrades into empty replies, yet nothing could compress it: the session is hidden from every list, the focused-chat /compress never targets it, and `-q` chat forwards slash text to the model. Group settings now lists each member with a "Compress history" action that resumes every session the room holds for that member (thread-scoped pointers, the legacy pre-thread pointer, or the pre-thread title as last resort) and runs the gateway's session.compress against the live runtime id — the exact RPC pair the reporter had to issue by hand over JSON-RPC. A 4007 (no such session) skips; anything else surfaces in the toast. requestForBot/host.request gain an optional per-request timeout so the 660 s compress budget the focused-chat /compress already uses applies here too instead of the socket's 30 s default reporting a false timeout. Slim redo of #102333 by @fangliquanflq (same action, without the auto-hygiene sweep and the group-turns facade appendage). 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.