migrate-memory

Agent memory migration works by reading source memory files, filtering out conversational residue, and preserving critical identity instructions and user preferences when writing to the target memory store during a provider switch.

The migration process requires access to the group workspace to read source memory files and write to the target memory store after updating the provider configuration for the specified agent group.

No, this Skill operates without external dependencies, relying solely on workspace access to read the source memory files and write the distilled identity instructions to the new provider-specific format.

This Skill prevents data loss by distilling durable facts, user preferences, and seed instructions from the source provider, ensuring they are preserved and written to the target memory store.

The Skill handles provider transitions by reading the original memory files, automatically translating the data shape, and writing the distilled memory to the target provider format.

To resolve memory loss, update the provider configuration and ask the agent to migrate memory for the specified group, which reads the workspace files and writes preserved identity instructions to the target store.