Skip to content

Local-first 🧠 memory for Hermes Agent that lives in your Obsidian vault and remembers project context. Nightly 😴 dream passes turn repeat corrections into confirmed preferences with measurable confidence. Adapters ship for Claude Code, Codex, and OpenClaw, with an MCP server for anything else.

TypeScript

docs: clarify Hermes multi-profile install limitation (#310)

Elysio Piresde14e79545b2
diff --git a/install/hermes.md b/install/hermes.md
index 1aed9b9c..d598fa19 100644
--- a/install/hermes.md
+++ b/install/hermes.md
@@ -158,6 +158,18 @@ location shadows the plugin `hermes plugins install` and
`hermes plugins update` manage, so an update appears to change nothing.
Remove such a copy and restart the gateway.
+**Current Hermes limitation:** The per-profile configuration above describes
+what this provider supports. With separate copies of this buildable plugin in
+two profile homes on the same machine, Hermes's plugin manager can fail to
+resolve its workspace on `hermes update` because both copies declare the same
+Python package name. The update may disable the plugin in the second profile.
+Until the host issue is resolved, avoid installing separate copies in multiple
+profile homes. See [Hermes issue #138702](https://github.com/NousResearch/hermes-agent/issues/138702)
+for the host-side status. A shared clone was reported as a workaround in
+[issue #308](https://github.com/itechmeat/open-second-brain/issues/308), but
+has not been validated on every Hermes version or platform. Updating a shared
+clone affects every profile that uses it.
+
### How Hermes discovers the provider
The primary route needs no packaging metadata at all: `hermes plugins