docs(integrations): drop Mem0 from marketing bullets#10
Merged
Conversation
Matches the same cleanup already on the integrations repo: remove Mem0 mentions from backend-agnostic pitch bullets on each coding-agent page and the overview. Rewrite as "or any other registered MemoryProvider" — same technical story, no third-party naming. Scope is deliberately limited to docs/integrations/**. SDK reference pages, the sdk/guides/mem0-backend.md how-to, and the introduction differentiation table are left alone per direction — those document existing SDK code or are intentional differentiation writing. Kept as-is (config contract, not marketing): - claude-code.md "To use Mem0 as the backend instead, set `\"provider\": \"mem0\"`" — documenting an actual enum value - openclaw.md configSchema snippet enum — mirrors the published manifest - codex.md `# or "mem0"` env comment — same reasoning
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.
Summary
Matches the Mem0 marketing cleanup already on the integrations repo. Removes Mem0 mentions from the backend-agnostic pitch bullets on each coding-agent page and the overview — rewritten as "or any other registered MemoryProvider".
Changed (4 marketing mentions)
docs/integrations/overview.md— backend-agnostic bulletdocs/integrations/coding-agents/claude-code.md— backend-agnostic bulletdocs/integrations/coding-agents/codex.md— backend-agnostic bulletdocs/integrations/coding-agents/openclaw.md— backend-agnostic bulletKept as-is (config contract, not marketing)
claude-code.md— "To use Mem0 as the backend instead, set"provider": "mem0"" paragraph; documents an actual enum valueopenclaw.md—configSchemasnippet enum; mirrors the published manifestcodex.md—# or "mem0"comment in env export exampleOut of scope (intentionally not touched)
SDK reference pages (
sdk/overview.md,sdk/guides/mem0-backend.md,sdk/concepts/provider-model.md, etc.) and the introduction differentiation table — those document existing SDK code or are intentional differentiation writing.Test plan
pnpm buildpasses withonBrokenLinks: 'throw'