skills.rest
jayho-k
jayho-kCOMMUNITY
Explore all skills by this author →
GitHub

mem0-oss-to-platform

Migrates projects from the self-hosted mem0 OSS SDK to the hosted mem0 Platform MemoryClient.

1|Updated Jan 13, 2022
Search Tags:#typescript#python#migration#sdk#code refactoring#mem0#memoryclient
One-click install
npx skills add https://github.com/jayho-k/TIL --skill mem0-oss-to-platform-jayho-k
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mem0-oss-to-platform
Source: https://github.com/jayho-k/TIL/tree/main/AI/mem0/code/mem0_code_analize/mem0/skills/mem0-oss-to-platform
Command: npx skills add https://github.com/jayho-k/TIL --skill mem0-oss-to-platform-jayho-k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moving an existing project from the self-hosted mem0 OSS SDK (the local Memory class with vector store, embedder, and LLM config) to the hosted mem0 Platform (MemoryClient) involves subtle API differences, config removal, and behavioral changes that are easy to get wrong. This Skill audits every mem0 touchpoint in a repo, writes a reviewable migration plan, and executes it only after approval. ## Core Features & Use Cases - Full Footprint Discovery: Finds every mem0 import, client initialization, config block, call site, dependency, env variable, and local infrastructure service across Python and TypeScript codebases. - Verified API Mapping: Confirms real method signatures against the installed SDK version, then maps each OSS call to its hosted equivalent (filters, top_k/topK, pagination) using a detailed reference mapping. - Plan-Then-Execute Workflow: Writes a concrete MEM0_MIGRATION_PLAN.md with inventory, change set, concerns, and verification steps, then stops for developer approval before editing any code. - Use Case: A team running a RAG service with Memory.from_config backed by a local Qdrant container wants to switch to the managed platform. The skill inventories all call sites, flags that existing local memories will not carry over, and migrates the code to MemoryClient with a smoke test against the real API. ## Quick Start Ask your assistant to migrate this project's mem0 setup from the self-hosted OSS SDK to the hosted mem0 Platform using my MEM0_API_KEY.

Frequently Asked Questions about mem0-oss-to-platform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from mem0 OSS to the mem0 Platform?▼

Replace the local Memory class and its vector_store/llm/embedder config with MemoryClient, which reads MEM0_API_KEY from the environment. This skill audits every call site, writes a migration plan for review, and executes the changes after you approve.

What changes between mem0 Memory and MemoryClient API calls?▼

For search and get_all, entity IDs like user_id must move into a filters dict, and get_all becomes paginated with page/page_size. TypeScript renames limit to topK, and add returns only ADD events on the v3 platform API.

Does migrating mem0 code to the platform move my existing memories?▼

No, code migration does not move stored memories; data in the local vector store and history DB stays behind and the hosted account starts empty. Data migration is a separate opt-in task of reading from the OSS store and re-adding to the hosted client.

Does the mem0 platform migration work for TypeScript projects?▼

Yes, it covers TypeScript and JavaScript where the OSS SDK is imported from mem0ai/oss and the hosted client is the default export of the mem0ai package. Option names are verified against the installed node_modules types before mapping.

What happens to my local Qdrant or Chroma dependencies after migrating?▼

Dependencies that existed only to back the local mem0 store, such as qdrant-client or chromadb, can be removed once confirmed unused elsewhere. Local infra services like a Qdrant docker-compose container are flagged for your confirmation rather than deleted automatically.

When should I not migrate from self-hosted mem0 to the platform?▼

Avoid migrating when self-hosting is required for compliance, data residency, or air-gapped deployments, since memory content moves to mem0's servers. The skill flags these cases as explicit decisions in the plan's concerns section.

Related Skills

Explore More Software Engineering Skills→
nhatnguyen1122nhatnguyen1122

mem0-oss-to-platform

Migrates projects from the self-hosted mem0 OSS SDK to the hosted mem0 Platform MemoryClient.

Community
Advanced
AlbertLin821AlbertLin821
2

mem0-test-integration

Execute native test suites and end-to-end smoke flows for Mem0 integrations.

Community
Advanced
mem0aimem0ai
64.5k

mem0-oss-to-platform

Migrates projects from the self-hosted mem0 OSS SDK to the hosted MemoryClient platform.

Official
Advanced
wipcomputerwipcomputer
3

wip-ai-devops-toolbox

Automate release management, license compliance, and repository security for AI-native projects.

Official
Advanced