docs(memory-providers): add Mnemosyne to provider documentation (#34271)#34356
Open
Bartok9 wants to merge 3 commits into
Open
docs(memory-providers): add Mnemosyne to provider documentation (#34271)#34356Bartok9 wants to merge 3 commits into
Bartok9 wants to merge 3 commits into
Conversation
…Research#34271) Mnemosyne is a community-maintained Hermes memory provider plugin that fills a documented gap in the bundled provider set: - Largest tool surface of any provider (19 tools vs Honcho's 5). - Only provider with hybrid semantic + FTS5 + temporal ranking in one query. - Only fully-local provider (beyond Holographic/ByteRover) with vector search, full-text search, and a knowledge graph in one engine. - Free + MIT + no API key + no quotas + no network egress. Per the issue's 'Minimal' acceptance criteria (no Hermes core code changes required), this PR: 1. Adds Mnemosyne to the front-matter description, the providers inventory line ('9 external memory provider plugins + 1 community provider'), and the example config-yaml comment. 2. Adds a full provider section under ### Memori with: - Best-for / Requires / Storage / Cost block - All 19 tools listed - Setup snippet showing pip install + plugin symlink + provider selection - Key capabilities summary - Lifecycle integration audit (which optional hooks are implemented vs not) - Explicit community-maintained status note pointing bug reports to the Mnemosyne project. 3. Adds a Mnemosyne row to the Provider Comparison table with a footnote distinguishing it from bundled providers. The 'community-maintained' framing is intentional: the issue's request was visibility, not promotion to first-party. The plugin- discovery system already supports user-installed providers via $HERMES_HOME/plugins/, so documentation is the only blocker. Refs: NousResearch#34271 Closes: NousResearch#34271 Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
I've closed #34679 in favor of this PR — credit where it's due for submitting first. I've layered the cross-reference updates (overview.md, memory.md, integrations/index.md + zh-Hans translations + stale '8 providers' fix) onto @Bartok9's branch via Bartok9/hermes-agent#2. If @Bartok9 merges that in, this PR will have both: the core Mnemosyne section + the cross-reference hygiene. One merge, everything clean. |
…s (+ zh-Hans) (#2) Adds Mnemosyne (and Memori) to the cross-reference lists in: - website/docs/integrations/index.md - website/docs/user-guide/features/overview.md - website/docs/user-guide/features/memory.md - website/i18n/zh-Hans/ integrations/index.md (zh-Hans) - website/i18n/zh-Hans/ overview.md (zh-Hans) Replaces stale '8 providers' wording with 'supported providers' for lower maintenance overhead. Co-authored-by: Bartok <bartok9@users.noreply.github.com>
The Mnemosyne cross-reference merge (#2) accidentally pulled in a local CodeGraph tooling artifact (.codegraph/.gitignore) that is unrelated to the docs change. Remove it to keep this PR scoped to documentation only.
Contributor
Author
Combined with @AxDSan's cross-reference additions + scope cleanupThanks to @AxDSan for the excellent follow-up — they opened a PR against this branch (Bartok9/hermes-agent#2) layering in the cross-reference updates this docs change was missing. I've merged it in, so this PR now covers: Original (this PR):
Added by @AxDSan (credit to them):
One cleanup from me: the merge accidentally pulled in a stray local CodeGraph tooling artifact ( Net result: 6 files, docs-only, all green, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #34271
Adds Mnemosyne as a community-maintained option in the memory-providers documentation. Per the issue's 'Minimal' acceptance criteria (no Hermes core code changes required), this PR is documentation-only:
### Memoriwith best-for / requires / storage / cost block, all 19 tools listed, setup snippet (pip install + plugin symlink + provider selection), key capabilities summary, and lifecycle-integration audit (which optional hooks are implemented vs not).The 'community-maintained' framing is intentional: the issue requested visibility, not promotion to first-party. The plugin-discovery system already supports user-installed providers via
$HERMES_HOME/plugins/, so documentation was the only blocker.🎻 Co-authored-by: Cursor cursoragent@cursor.com