Skip to content

The agent that grows with you

chore(catalog): review disclosure for hermes-lcm-x

teknium1cd6c283dcfdd
diff --git a/plugin-catalog/hermes-lcm-x.yaml b/plugin-catalog/hermes-lcm-x.yaml
index 25f2b603338..f464a649c6a 100644
--- a/plugin-catalog/hermes-lcm-x.yaml
+++ b/plugin-catalog/hermes-lcm-x.yaml
@@ -2,20 +2,7 @@ name: hermes-lcm-x
title: LCM-X
repo: https://github.com/electricsheephq/lcm-x
sha: c67d7633d963a2ffd24cf90995189ee58e2f88c7
-description: 'Lossless memory for long sessions: LCM-X keeps every turn in a local store instead of compacting it away, and the agent
- can search and expand it. The store is local SQLite (lcm.db) with a recoverable DAG of summaries over it and 15 lcm_*
- tools for search, recall and expansion. Select it with context.engine: lcm-x. Upgrading from hermes-lcm (breaking in
- v0.24.0): stop Hermes, then in plugins.enabled replace hermes-lcm with hermes-lcm-x and run exactly one LCM copy (the
- install script prints the steps; the old engine name lcm still resolves with a deprecation warning); lcm.db and the lcm:
- config block are unchanged. Summaries use the model Hermes is configured with. Disclosure — optional semantic recall
- (embeddings_enabled, off by default) sends message text to the embedding provider you configure (Voyage via
- VOYAGE_API_KEY, an OpenAI-compatible endpoint, or a local Ollama); in-process FastEmbed keeps it on the machine after a
- one-time model download. For known cloud providers the provider-bound copy is privacy-transformed by default
- (LCM_EMBEDDING_PRIVACY_ENABLED=false opts out), while lcm.db keeps the raw text. Every turn (user, assistant and tool
- output) is stored in plaintext in lcm.db (secret redaction at rest is opt-in). The engine also reads Hermes'' state.db
- read-only for session lineage, reads private AIAgent attributes via the call stack on Hermes builds without subagent
- hooks, and runs git on its own install directory for lcm_status/lcm_doctor; tiktoken may fetch its BPE file on first
- use.'
+description: "Lossless memory for long sessions: LCM-X keeps every turn in a local store instead of compacting it away, and the agent can search and expand it. The store is local SQLite (lcm.db) with a recoverable DAG of summaries over it and 15 lcm_* tools for search, recall and expansion. Select it with context.engine: lcm-x. Upgrading from hermes-lcm (breaking in v0.24.0): stop Hermes, then in plugins.enabled replace hermes-lcm with hermes-lcm-x and run exactly one LCM copy (the install script prints the steps; the old engine name lcm still resolves with a deprecation warning); lcm.db and the lcm: config block are unchanged. Summaries use the model Hermes is configured with. Disclosure — optional semantic recall (embeddings_enabled, off by default) sends message text to the embedding provider you configure (Voyage via VOYAGE_API_KEY, an OpenAI-compatible endpoint, or a local Ollama), and once enabled new summaries are embedded automatically in the background; in-process FastEmbed keeps it on the machine after a one-time model download. For known cloud providers the provider-bound copy is privacy-transformed by default (LCM_EMBEDDING_PRIVACY_ENABLED=false opts out), while lcm.db keeps the raw text. Every turn (user, assistant and tool output) is stored in plaintext in lcm.db (secret redaction at rest is opt-in), and oversized tool outputs are by default written as plaintext files under HERMES_HOME/lcm-large-outputs and replaced in the model's context by recoverable references. The engine also reads Hermes' state.db read-only for session lineage, reads private AIAgent attributes via the call stack on Hermes builds without subagent hooks, and runs git on its own install directory for lcm_status/lcm_doctor; tiktoken may fetch its BPE file on first use."
maintainer: 100yenadmin
tier: community
category: memory