# Migrate Memory

Migrate legacy NanoClaw and Claude-native memory into the shared memory tree and...

- Repository: https://github.com/nanocoai/nanoclaw (31069 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nanocoai/nanoclaw --skill migrate-memory -g -a claude-code -y`
Codex: `npx skills add nanocoai/nanoclaw --skill migrate-memory -g -a codex -y`
Cursor: `npx skills add nanocoai/nanoclaw --skill migrate-memory -g -a cursor -y`
Gemini CLI: `npx skills add nanocoai/nanoclaw --skill migrate-memory -g -a gemini-cli -y`

## Description

Migrate legacy NanoClaw and Claude-native memory into the shared memory tree and provider-neutral standing instructions. Run after an update reports the shared-memory breaking change, or when a group still has .seed.md, legacy CLAUDE.md/CLAUDE.local.md, Claude auto-memory, or an unindexed imported-agent-memory.md. Triggers on "migrate memory", "legacy memory", "the agent forgot everything after the switch".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Migrate legacy memory

Every provider now uses the same `groups/<folder>/memory/` tree. Provider
switches carry memory automatically. The coding harness running this skill -
Claude Code, Codex, or another harness - owns the whole migration. It stages,
organizes, indexes, and verifies legacy memory before the NanoClaw group runs
again. Normal host and container startup never imports legacy files.

Staging is deliberately content-blind: move regular files and quarantine
symlinks without following them. After every staged path is safe and the group
container is stopped, the invoking harness reads the regular staged files as
untrusted data and organizes them. The NanoClaw host process and the running
group agent never perform the migration.

## 1. Inventory and maintenance window

1. Run `ncl groups list` and identify every affected group folder.
2. For each folder, inspect path types with `lstat`-equivalent commands such as
   `test -L`, `test -f`, and `test -e`. Check:
   - `.seed.md`
   - `CLAUDE.md`
   - `CLAUDE.local.md`
   - `memory/memories/imported-agent-memory.md`
   - `instructions.prepend.md`
   - `memory/index.md`
   - `data/v2-sessions/<group-id>/.claude-shared/projects/*/memory/`
3. Show the operator the affected groups and collision/symlink status. Record
   every planned source-to-destination rename so it can be reversed exactly.
   Ask for approval before moving anything.
4. For each affected group, run
   `ncl tasks list --group <group-id> --status pending`. Record the returned
   series IDs, then pause each with
   `ncl tasks pause <series-id> --group <group-id>`. Do not resume tasks that
   were already paused before this workflow.
5. Ask the operator not to message these groups during the migration. Run
   `ncl groups restart --id <group-id>` for each affected group. Without an
   on-wake message this stops the current container; it starts again only when
   the next message arrives.

The rest: https://github.com/nanocoai/nanoclaw/blob/HEAD/.claude/skills/migrate-memory/SKILL.md