| 123456789101112131415161718192021222324252627282930313233343536373839 |
- name: hermes-lcm-x
- title: LCM-X
- repo: https://github.com/electricsheephq/lcm-x
- sha: 984a40045372f1f24a87d060194786f4d1843b90
- subdir: plugin
- 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 16 lcm_* tools for search, recall and expansion (lcm_memory only with LCM_ENTITIES_ENABLED=1). 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 — local semantic recall is on by default once its dependency companion is installed (hermes plugins install electricsheephq/lcm-x/companions/hermes-lcm-x-local-embeddings --ref <the LCM-X commit>; it carries fastembed): summaries and message chunks are embedded in-process with BAAI/bge-small-en-v1.5 after a one-time model download, in the background, and stay on the machine. Without the companion, recall answers from full text and lcm_doctor prints the install command; on hosts with 2 or fewer effective CPUs the default answers from full text unless LCM_EMBEDDINGS_ENABLED=true; LCM_EMBEDDINGS_ENABLED=false turns semantic recall off. Cloud embedding providers (Voyage via VOYAGE_API_KEY, an OpenAI-compatible endpoint, or a local Ollama) send message text to that provider and run only with LCM_EMBEDDINGS_ENABLED=true and an explicit model. 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); on gateway platforms the sender's platform user ID is recorded with each user message by default (LCM_SENDER_CAPTURE=0 turns it off), 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
- requires_hermes: '>=0.21.3'
- docs_url: https://github.com/electricsheephq/lcm-x#readme
- version: "0.29.1"
- image: https://raw.githubusercontent.com/electricsheephq/lcm-x/3a4a08ff501347a79669fab51444c471b09b551d/docs/media/banner.png
- platforms: []
- capabilities:
- provides_tools:
- - lcm_grep
- - lcm_recall
- - lcm_query_state
- - lcm_compute
- - lcm_compile_evidence
- - lcm_evidence_pack
- - lcm_retrieve
- - lcm_recent
- - lcm_load_session
- - lcm_describe
- - lcm_expand
- - lcm_expand_query
- - lcm_status
- - lcm_inspect
- - lcm_doctor
- - lcm_memory
- provides_hooks:
- - pre_llm_call
- - post_llm_call
- - subagent_start
- - subagent_stop
- provides_middleware: []
- requires_env: []
|