ruvnet / rvf-manage
Manage RVF (Ruflo Vector Format) files for portable agent memory and cross-platform transfer
RVF Management
Manage RVF files for portable, transferable agent memory.
When to use
When you need to export agent memory to RVF format for backup, transfer between projects, or share knowledge between teams.
Steps
- List memories — call
mcp__plugin_ruflo-core_ruflo__memory_listto see all stored memories - Export —
npx @claude-flow/cli@latest memory export -o <file> [-n <namespace>] [-f json|csv|binary](vectors included by default;--include-vectors falseto drop them). Pick the output path inside the project, never an existing file you have not read - Import —
npx @claude-flow/cli@latest memory import -i <file> [-n <namespace>](merges and skips duplicates by default), or callmcp__plugin_ruflo-core_ruflo__memory_import_claudeto pull in Claude Code auto-memories - Migrate — call
mcp__plugin_ruflo-core_ruflo__memory_migratefor format upgrades - Stats — call
mcp__plugin_ruflo-core_ruflo__memory_statsfor storage metrics
RVF format
RVF (Ruflo Vector Format) stores:
- Vector embeddings (384-dim ONNX)
- Metadata (timestamps, namespaces, tags)
- Causal relationships between entries
- Session context and agent scope
Transfer between projects
Copy patterns from another local project (nothing leaves the machine):
npx @claude-flow/cli@latest hooks transfer from-project --source /path/to/other/projecthooks transfer store is different: it is the pattern marketplace on the public IPFS registry (list, search, download, publish). Never run publish for project memory unless the user asks for it, and scan the content for PII and secrets first (mcp__plugin_ruflo-core_ruflo__transfer_detect-pii). Anything published may be cached and cannot be recalled.
Exported files are not encrypted by the at-rest setting (see the plugin README); treat them as sensitive if the memory is.