Memory Transfer

Transfer memory files from one OpenClaw agent to another. Use when you need to migrate memory, configuration, or context from one agent to another agent.

Security Scan

The skill mostly does what it says (copy agent memory files locally) but its runtime instructions and code allow reading and copying arbitrary filesystem paths (no path sanitization), which can lead to unintended data access/exfiltration and is not called out in the description.

Purpose & Capability

Name, description, SKILL.md, and memory-transfer.js all align: the tool lists and copies memory files between agent workspaces under /home/node/.openclaw. No unrelated capabilities are requested.

Instruction Scope

SKILL.md instructs the agent to read/copy files from agent workspaces (expected), but the script accepts arbitrary agent IDs and does not sanitize them. Supplying an absolute path or path traversal (e.g., '/etc', '../somepath') as an agent-id can cause the tool to read or copy files outside the intended workspace base. The instructions do not warn about this risk or restrict operations.

Install Mechanism

No install spec; this is an instruction-only skill with a single local Node script (no remote downloads or package installs). This minimizes install-time risk.

Credentials

The skill requires no environment variables, credentials, or external services. The requested access (local filesystem reads/writes) is consistent with its stated purpose, but scope of filesystem access is broader than it appears because agent IDs can resolve outside the workspace base.

Persistence & Privilege

always is false and the skill does not request persistent agent-wide privileges. It runs on-demand and only manipulates files it can reach based on supplied paths/agent IDs.

What to consider before installing

This tool is coherent with its stated purpose (copying agent memory files), but it lacks path validation: passing absolute paths or '../' style agent IDs can make it read or copy arbitrary files on the host. Before installing or running it, consider: (1) review the code locally (already included) and test only in a safe environment; (2) run with a low-privilege account that cannot read sensitive files; (3) prefer using the --dry-run flag to verify which files will be affected; (4) harden the script by normalizing and validating paths (reject absolute paths and any path segments with '..', ensure resolved path startsWith the workspace base); (5) avoid running on multi-tenant hosts or systems containing sensitive PII unless you trust the inputs and have backups. If you need, ask the developer to add path sanitization and explicit confirmation prompts before copying.

Memory Transfer Skill

Transfer memory files and context between OpenClaw agents.

Use Cases

• Migrate memory from main agent to a sub-agent
• Copy user preferences to a new agent
• Share project context between agents
• Backup agent memory before resets

How It Works

1. Read source agent's workspace memory files
2. Copy to target agent's workspace
3. Optionally merge with existing memory

Commands

List available agents

ls /home/node/.openclaw/

Transfer memory from source to target

node memory-transfer.js transfer <source-agent-id> <target-agent-id>

Transfer specific memory file

node memory-transfer.js transfer <source-agent-id> <target-agent-id> <memory-file>

List agent memories

node memory-transfer.js list <agent-id>

Preview transfer (dry run)

node memory-transfer.js transfer <source> <target> --dry-run

Examples

Transfer main agent memory to coder agent

node memory-transfer.js transfer main coder

Transfer specific date memory

node memory-transfer.js transfer main coder 2026-03-01.md

Preview what would be transferred

node memory-transfer.js transfer main coder --dry-run

Agent Workspaces

OpenClaw agent workspaces are typically at:

• /home/node/.openclaw/workspace-<agent-id>/
• Main agent: /home/node/.openclaw/workspace-main/

Memory files:

• MEMORY.md - Long-term memory
• memory/YYYY-MM-DD.md - Daily memories