teknium1
57c4e1d963
A dashboard/desktop backend (and the per-profile cron ticker) serves sessions of several profiles through the HERMES_HOME contextvar override while gateway.multiplex_profiles stays off. _mcp_registry_scope() keyed every MCP connection by the bare server name in that mode, so the first profile to discover `zernio` owned the only connection and every later served profile — including one whose config carries a different Authorization header — called the server through it and got the other account's data back (#111151). The registry scope now follows the served home: a routed profile (an override naming a home other than the process home) gets the same per-profile overlay the multiplexer uses, so a same-named server with other credentials is a separate connection, discovery for profile B is a connect candidate instead of "already connected", and status/tool views stay per profile. Single-profile processes (no override) keep bare keys, byte-identical to before. Fixes #111151 Credit: #111158 by @KoNit-K located the inert flag on hermes_cli surfaces; its fix (activating fail-closed multiplex secret scoping from config.yaml on the dashboard) is not taken — the connection-key seam, not the secret-scope mode, is what leaks the connection, and flipping the process-wide mode from the dashboard would change credential resolution for every code path in it.
Website
This website is built using Docusaurus, a modern static website generator.
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.