HermesMemory

@Teknium @nousresearch Deploy token on base @bankrbot Name : HermesMemory Ticker : MEMORY Description : while external memory provider sections are shown only when configured. X handle : x.com/hermesmemory Website : github.com/xraysight/herm…

memory and fact cards from the local SQLite store, with search and limit filters. @Teknium @nousresearch

🚀 Introducing HermesMemory — where memory meets intelligence. Not all data deserves to be forgotten. HermesMemory is designed to transform information into lasting knowledge, helping AI agents remember, learn, and evolve with every interaction. github.com/xraysight/herm…

The browser cannot and should not read local files or SQLite directly. plugin_api.py runs inside the dashboard process, can resolve the active profile's HERMES_HOME, and can safely expose a narrow JSON API.

Built-in memory(add) may mirror into holographic memory, but replace, remove, and direct file edits do not reliably mirror.

Mnemosyne maintains embeddings, Memoria-derived structured tables, graph rows, sleep/consolidation flows, and provider-level recall semantics.

Built-in memory has limits, delimiter parsing, locking, duplicate handling, and prompt-injection scanning.

reliably mirror. A dashboard that writes directly to files or SQLite can silently corrupt memory semantics.

Mnemosyne support follows Hermes' Mnemosyne memory provider convention. The plugin reads non-secret state

Honcho support follows Hermes' bundled honcho memory provider convention and reuses Hermes' provider helpers for config resolution and client creation. Supported config locations are resolved by Hermes, including:

The API key is only used server-side to instantiate mem0.MemoryClient; it is never returned in plugin responses. The plugin performs read-only calls:

mem0.json may technically override these values if fields are present, matching Hermes' provider behavior, but keeping api_key in