docs: document multi-agent Hermes and operating profiles - #242
Conversation
Adds the operating-profiles page the Ansible role already links to, fixes the Hermes agent page's outdated "multi-agent can be layered on later" framing, and adds a diagram of the container/agent/profile hierarchy.
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_23375530-7696-4801-b272-e5843a7fb1c8) |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request documents Hermes operating profiles, detailing how tools and credentials are scoped per job within an agent, and explains the architecture for running multiple independent agent identities side-by-side. Feedback was provided to clarify a conceptual contradiction regarding how independent $HERMES_HOME directories share the same memory bank.
The page said every profile of one agent reads and writes the same memory bank while also describing a profile as a fully independent HERMES_HOME, which reads as a contradiction against the built-in MEMORY.md / USER.md files documented on the agent page. State the mechanism: the shared bank is the agent-keyed bank in the network memory provider, not the per-directory files. Assisted-by: Claude:claude-opus-5[1m]
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_4cf556b3-cd65-4b60-8a27-5605c070bad9) |
Summary
Test plan
jq empty docs.jsonmint broken-linksscripts/validate-mermaid.shNote
Low Risk
Documentation-only changes with no runtime, auth, or data-path impact.
Overview
Documents how Hermes is actually deployed today — separate agent identities (
hermes,donna) vs named profiles inside one agent — and adds the missing Hermes operating profiles page that Ansible/docs already pointed at.On Self-hosted AI agent, containment is reframed: LXC is the blast-radius boundary; profiles only scope tools and credentials (shared user, shared memory). A new More than one agent section plus a Mermaid diagram show isolated containers and profile rosters under
hermes. The outdated “profiles/Kanban can be layered on later” line is removed; Slack is stated as the sole chat surface.The new page explains per-job
HERMES_HOMEprofiles (override-not-merge config, one gateway/Kanban/Slack per agent), that memory is not profile-isolated, and a roster table (default,splunk-admin,homelab-admin,github-maint) with mission and deny lists. docs.json adds the page under AI development nav.Reviewed by Cursor Bugbot for commit 6f77c5d. Bugbot is set up for automated code reviews on this repo. Configure here.