f9d6d04332
A hand-written Linux daemon unit (systemd user unit / XDG autostart entry running `cua-driver serve`) can be dead for days — crash loop, stopped, never started — while `hermes computer-use doctor` and `status` report a healthy binary: the runtime contract only checks the binary (`manifest`), and nothing ever connected to the daemon socket (#114748). - tools/computer_use/cua_backend.py::cua_daemon_listening — socket-level liveness via `cua-driver status [--socket PATH]` (rc 0 = a daemon answered, "not running" = dead, anything else = unknown). Never raises. - tools/computer_use/doctor.py::cua_daemon_units — one scan of the units that run cua-driver (kind, unit, exec target, runs `serve`, `--socket` path with `%h` expanded); the pruned-Exec guard now filters that list instead of re-scanning. - doctor.py::_apply_daemon_liveness_guard — per `serve` unit: `pass` when its socket answers, `fail` (degrading `ok`) when not, with the hint that a driver reinstall does not start the daemon. Unconfigured daemons are never probed: on Linux the MCP runtime needs none, so a silent default socket is normal. - `hermes computer-use status` prints the dead-daemon line and exits 1. - docs: the Linux daemon-unit paragraph under the doctor section. Not changed: _maybe_repair_runtime_contract. The repair is gated on the binary-level contract only; a dead daemon never enters it, so a reinstall was never triggered by the daemon (the `.release_installed/<version>` marker the reporter saw is written by cua-driver itself on any first run of the binary — observed via strace of `cua-driver status` under a fresh HOME). Supersedes #114928 (@Finn763): same finding, ~600-line implementation with a new module and a repair-gate rewrite; this is the ~90-line version on the existing doctor seams.
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.