docs: document multi-agent Hermes and operating profiles - #242
docs: document multi-agent Hermes and operating profiles#242JacobPEvans-personal wants to merge 1 commit into
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 isolation boundary is tools and credentials — not memory.** Every | ||
| profile of one agent reads and writes the same memory bank. This is | ||
| deliberate: it is what lets a `default`-profile job recall a card's findings | ||
| after its assignee moves — but it means a narrowly scoped profile can still | ||
| recall anything any other profile of that agent ever wrote. Profile scoping | ||
| is not a data boundary. |
There was a problem hiding this comment.
There is a slight conceptual tension between how profiles and memory are described here and in hermes-agent.mdx:
hermes-agent.mdxstates that the built-in memory (MEMORY.md/USER.md) is stored under$HERMES_HOME.- This page states that a profile is a fully independent
$HERMES_HOMEdirectory (line 13), but also that every profile of one agent reads and writes the same memory bank (line 25).
To prevent confusion for operators configuring or troubleshooting these profiles, please clarify how this shared memory bank is structurally achieved across independent $HERMES_HOME directories (e.g., via symlinking the memory files, shared volume mounts, or if the shared memory bank refers specifically to the network-based Hindsight provider).
Summary
Test plan
jq empty docs.jsonmint broken-linksscripts/validate-mermaid.shNote
Low Risk
Documentation and nav only; no runtime, auth, or infrastructure code changes.
Overview
Documents how Hermes actually runs today: separate agent identities (
hermes,donna) each with their own container, Slack app, credentials, and memory — not profiles stacked on one agent.Clarifies that profiles are a tool/credential envelope inside one agent (shared gateway, shared memory, override-not-merge config). Adds a dedicated page with the current roster (
default,splunk-admin,homelab-admin,github-maint) and a mermaid diagram of the container/profile split. Wires the page into nav.Reviewed by Cursor Bugbot for commit 190b5f8. Bugbot is set up for automated code reviews on this repo. Configure here.