Migrate an agent group's durable memory between provider stores.
npx skills add https://github.com/Bartunek/nanoclaw --skill migrate-memory-bartunek
Please help me install this Agent Skill. Skill: migrate-memory Source: https://github.com/Bartunek/nanoclaw/tree/main/.claude/skills/migrate-memory Command: npx skills add https://github.com/Bartunek/nanoclaw --skill migrate-memory-bartunek
Carry an agent group's memory across a provider switch, in either direction (e.g. Claude ↔ Codex, or any provider to/from another). Run after the operator switches a group's provider with ncl groups config update --provider. The coding agent reads the source provider's memory store, distills it into the target provider's store, and restarts the group. Triggers on "migrate memory", "carry memory over", "the agent forgot everything after the switch".
Execute the memory migration for the selected group after confirming the source and target providers.
High-intent search queries and answers about installing and using this skill.
To migrate agent memory after a provider switch, run the memory migration tool after updating the group's provider configuration. It reads the source memory store, distills durable content, writes to the target store, and restarts the group to ensure behavioral continuity.
An agent forgets everything after a provider switch because the durable memory remains stored in the previous provider's memory store. Memory migration transfers this identity and configuration data from the source store to the new target store.
Memory migration supports both flat memory representations like CLAUDE.local.md and scaffold tree structures within a memory directory. It reads the source provider's memory shape and distills the durable content directly into the target provider's store.
You can carry memory over between Claude and Codex providers in either direction. The migration tool reads the source provider's memory store, infers the durable content, and writes it to the target provider's store before restarting the group.
The best way to preserve agent identity when changing providers is to execute a memory migration for the selected group. This distills durable content such as preferences and configurations from the source store into the target store, maintaining continuity.
You need to update the group provider configuration before migrating memory. The memory migration process is designed to run after the operator switches a group's provider, reading the old source store and writing to the newly configured target store.
tharunramagiriMigrate agent memory stores between flat files and scaffolded directory trees.
unclehowellStore durable facts and synchronize memory across agent sessions.
DNG-aiStore, search, and manage persistent AI agent memories across sessions.
krishagelStore and retrieve user preferences with confidence scores in structured JSON files.
