From mem0
Imports memories from a mem0 export file (Markdown) into the current project. Use when migrating, restoring from backup, or setting up a new project with existing knowledge.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mem0:importThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Import memories from a mem0 export file into the current project.
Import memories from a mem0 export file into the current project.
If the user provided a filename as an argument to /mem0:import <filename>, use that file.
Otherwise, list .md files in the current directory whose names contain mem0-export:
ls -1 *.md 2>/dev/null | grep mem0-export || echo "No export files found"
If multiple files are found, ask the user which one to import. If none are found, print:
No mem0-export files found in the current directory.
Run /mem0:export first, or provide the filename: /mem0:import <path-to-file>
Determine the plugin root. Use the appropriate variable for the current platform:
${CLAUDE_PLUGIN_ROOT}${CODEX_PLUGIN_ROOT}${CURSOR_PLUGIN_ROOT}Run the parser script to extract memory records as JSON:
python3 "<PLUGIN_ROOT>/scripts/parse_export_file.py" "<path-to-export-file>"
This outputs a JSON array where each element has:
id — original memory ID (for reference only; a new ID will be assigned on import)type — metadata typeconfidence — metadata confidence valuebranch — metadata branchfiles — list of associated filescategories — list of categoriescontent — the memory textIf the script fails or outputs [], print:
Failed to parse <filename> or file contains no valid memory blocks.
and stop.
Determine the active identity:
user_id from MEM0_USER_ID env var, else $USER, else "default"project_id (used as app_id) from MEM0_PROJECT_ID env var, or via the project resolverFor each record in the parsed JSON array, call add_memory with:
text="<record.content>"user_id=<active_user_id>app_id=<active_project_id>metadata={
"type": "<record.type>" (if non-empty)"confidence": "<record.confidence>" (if non-empty)"branch": "<record.branch>" (if non-empty)"files": <record.files> (the list, if non-empty)"source": "import"}infer=FalseNotes:
id — the platform assigns a new ID.content is empty (the parser already filters these, but be defensive).Imported <N> memories into project <project_id>
Where <N> is the number of successfully imported memories.
If any failed:
Imported <N>/<total> memories into project <project_id> (<failed> failed)
--tools)When invoked with --tools (e.g., /mem0:import --tools), detect and import
from competing AI tool configuration files:
| Tool | File/directory |
|---|---|
| Cursor | .cursorrules |
| GitHub Copilot | .github/copilot-instructions.md |
| Cline | memory-bank/ (directory of .md files) |
| Continue | .continue/rules.md |
test -f .cursorrules && echo "cursor: .cursorrules"
test -f .github/copilot-instructions.md && echo "copilot: .github/copilot-instructions.md"
test -d memory-bank/ && echo "cline: memory-bank/"
test -f .continue/rules.md && echo "continue: .continue/rules.md"
List found files, ask which to import (numbers, comma-separated, or "all"). If none found:
No competing tool configuration files found.
Checked: .cursorrules, .github/copilot-instructions.md, memory-bank/, .continue/rules.md
For each selected tool:
python3 "<PLUGIN_ROOT>/scripts/import_competing_tools.py" <tool> --path <file>
Tools: cursorrules, copilot, cline, continue.
Imported <N> memories into <project_id> (cursor: <N>, copilot: <N>)
Notes: infer=False, tagged metadata.source=<tool>-import, sections <50 chars
skipped, chunks >10k chars truncated, safe to re-run (deduplication handles it).
When invoked with a path to Claude Code's native MEMORY.md file (typically
~/.claude/projects/<proj-key>/memory/MEMORY.md), or when on_session_start.sh
detects native auto-memory and the user chooses to import:
- bullet prefix).#).add_memory with:
text="<line>"user_id=<active_user_id>app_id=<active_project_id>metadata={"type": "task_learning", "source": "memory-md-import", "confidence": 0.8}infer=FalseImported <N> memories from MEMORY.md into project <project_id>To avoid duplicate memory systems, add to ~/.claude/settings.json:
"autoMemoryEnabled": false
This handles the cold-start gap when a user has been using Claude Code's native memory and switches to mem0.
<PLUGIN_ROOT>/scripts/parse_export_file.py, print an error and stop.add_memory calls fail consistently (e.g. auth error), report the issue and stop early.npx claudepluginhub mem0ai/mem0 --plugin mem0Exports project memories to a portable Markdown file for backup or migration. Useful for archiving, sharing state, or moving between projects.
Manages workspaces and memories in the Recuerd0 platform via the recuerd0 CLI. Proactively captures architectural decisions, debugging resolutions, user preferences, and non-obvious discoveries.
Organizes, extracts, prunes, and verifies Claude Code persistent memory files to keep MEMORY.md under the 200-line truncation limit and topic files up to date with project state.