3acd949217
"Keep computer awake" was a boolean: off, or a machine-global power-save blocker held for as long as Hermes Desktop is open. That is the wrong shape for its own stated purpose. An unattended overnight run dies when the machine sleeps unless the user predicted, before starting, that they would need the toggle — and a user who did flip it leaves a laptop pinned awake all week, including the idle hours after the run finished (#101991). Main already knows, live, whether any turn is in flight: `mergeActiveWork(activeWorkByWebContents.values()).count > 0` is the exact expression that drives stream throttling. This change wires the blocker to that same signal behind a three-way mode: off never hold the blocker (unchanged default) while-working hold it only while a turn is in flight; release at idle always hold it whenever the app is open (what `on` used to mean) Both persisted copies migrate in place. The renderer's localStorage boolean (`hermes.desktop.keepAwake.v1`) and main's `keep-awake.json` `{ on }` are read once and mapped `true -> always`, `false -> off`, so an existing user sees exactly the behaviour they had. The IPC channel keeps its name and accepts either the mode or the old boolean. An unrecognised saved value is refused rather than trusted and falls back to `off`. No new listener, timer, or IPC channel: `updateStreamThrottleFromActiveWork` computes the merged picture once and hands it to both consumers, and the cold-launch apply reads the mode instead of the flag. No trailing delay between back-to-back turns — a sub-second release cannot let a machine sleep, and `powerSaveBlocker` start/stop are cheap. The policy is three pure functions in power-save.ts (parse, read, wanted) so it is testable without the main process; main only wires them. (cherry picked from commit c6dab931a2891ea7026eea2c07c271bcf48446b9)
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.