6489ef982c
Main claims Cmd/Ctrl+W on every window (window-accelerator's before-input-event + preventDefault, kept for the #105498 swallow guard and the Win/Linux close path) and routes it to the renderer via hermes:close-preview-requested; the renderer's close rung maps any focused [data-terminal] to closeActiveTerminal(), so the chord closed the pane and killed the live shell instead of reaching xterm as readline unix-word-rubout (#65457). Route it the way #108550 routes Cmd/Ctrl+R: keep main's claim exactly as-is, and add the missing terminal rung in the renderer. - TerminalInstance (the user PTY) gains [data-interactive-terminal]; the read-only agent mirror keeps only [data-terminal], so its tab stays deliberately closeable (the #65524 breadth complaint). - The terminal handle registry (terminal-context-menu) keys by the [data-terminal] scope rather than the nested xterm host — the same fix #108550 carries — and grows a wordErase verb: the user terminal re-delivers the ^W byte to its PTY, the agent mirror's is null. - The close-preview IPC rung (use-desktop-integrations) and the view.closeTab keybind dispatch (use-keybinds) both consume the bare platform chord through that verb instead of closing; Shift / Alt / rebound variants keep closing. - The non-mac Window>Close menu item becomes click-only (registerAccelerator: false): the 'close' role's default CommandOrControl+W accelerator would claim the chord before the before-input-event run. Clicking it still closes the window. Co-authored-by: Kyssta <218078013+kyssta-exe@users.noreply.github.com> Co-authored-by: percival <ignacio@agenticolabs.io>
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.