docs: finish Mimir -> Mneme prose rename in remaining docs#321
Merged
Conversation
Code identifiers, GHCR image, repo URLs, and registry metadata were already renamed in #318/#319. This pass covers the product-name prose still saying "Mimir" in awesome-mimir.md, CONTRIBUTING.md, SUPPORT.md, SBOM/federal-buyers/EXPORT-CONTROL docs, the three MCP client integration guides, the three vs-competitor comparison docs, and the four integrations/ READMEs. Deliberately left "mimir"/"Mimir" where it's a real back-compat identifier rather than prose: - mimir_* MCP tool wire names (unchanged, back-compat guaranteed) - ~/.mimir/data/mimir.db path examples (unchanged, back-compat path) - The CLI binary invocation and "mcpServers": {"mimir": {"command": "mimir", ...}} config key — install.sh symlinks mneme -> mimir, so "mimir" is still the primary working command today - PyPI package/module names and classes (mimir_autogen, mimir_crewai, mimir_langgraph, mimir-persist, MimirStore, MimirMemoryTool, MimirMemory) and their real "binary=\"mimir\"" code defaults - docs/SBOM.md's literal crate/component identifiers (crates.io:mimir@2.0.0, Component name: mimir) - External repo name (hermes-mimir-plugin) and this repo's own filenames (awesome-mimir.md, mimir-vs-*.md) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Base commit
Branched fresh from
org/mainat59d56571d9b9fd0d6cf53d2fb8f019109408b7cd("Release v2.8.0: finish the Mimir -> Mneme rename (URLs, registry metadata) (#319)"), confirmed viagit merge-base --is-ancestorbefore and after committing. This branch is a clean 1-commit ahead of that release commit — it does not touch version numbers, the GHCR image tag, the registry identity comment, or any repo URL (all of those are correct as of #319 and are left untouched here).What this does
Code identifiers, the GHCR image, repo URLs, and registry metadata were already renamed in #318/#319. What was left was product-name prose — the word "Mimir" used as the product's display name in running text/headings — across 16 docs/README files that hadn't been touched yet:
awesome-mimir.mdCONTRIBUTING.mdSUPPORT.mddocs/SBOM.mddocs/federal-buyers.mddocs/EXPORT-CONTROL.mddocs/integration/claude-code.mddocs/integration/cursor.mddocs/integration/general-mcp.mddocs/comparison/mimir-vs-mem0.mddocs/comparison/mimir-vs-letta.mddocs/comparison/mimir-vs-zep.mdintegrations/README.mdintegrations/autogen/README.mdintegrations/crewai/README.mdintegrations/langgraph/README.mdgit diff --statconfirms only these 16 files changed.What was deliberately left as "Mimir"/"mimir"
mimir_remember,mimir_recall,mimir_as_of, etc.) — back-compat-guaranteed, unchanged everywhere.~/.mimir/data/mimir.dbpath examples — still valid via back-compat, unchanged."mcpServers": {"mimir": {"command": "mimir", ...}}config key in the integration guides and comparison docs.scripts/install.sh(already renamed, out of scope here) installs the binary asmnemebut also creates amimirsymlink for back-compat (ln -sf "$BIN_DIR/mneme" "$BIN_DIR/mimir"), and its own printed setup instructions still saymimir. Somimiris genuinely the primary documented/working command today — left as-is rather than "corrected" tomneme.mimir_autogen,mimir_crewai,mimir_langgraph,mimir-persist,MimirStore,MimirMemoryTool,MimirMemory. Also left their realbinary="mimir"code defaults alone (confirmed againstintegrations/*/mimir_*/__init__.py, which still literally defaults to"mimir"— not touched since those source files are out of scope).docs/SBOM.md's literal crate/component identifiers (crates.io:mimir@2.0.0,Component name: mimir,Package: mimir v2.0.0) — kept verbatim per the literal crates.io package identifier convention; only the doc's H1 heading ("Mneme SBOM") was changed.hermes-mimir-plugin(a different repo's name/URL) and this repo's own filenames referenced in links (awesome-mimir.md,mimir-vs-mem0.md,mimir-vs-letta.md,mimir-vs-zep.md).Everything else — headings, sentences, table cells, explanatory prose describing the product — now reads "Mneme".
Not merging; leaving open for review.
🤖 Generated with Claude Code