Last updated: October 19, 2026
Short answer: Export the agent's memory to a file outside the agent, then have the new session or new agent read that file at startup. With Fulcra, the agent writes its memory to a path such as /agents/memory/backup.md; every write is versioned, so you can restore an earlier copy, and any agent you connect can read it back.
Agent memory usually lives inside the agent: a MEMORY.md, a local database, or the provider's own memory feature. Start a fresh session, move to a new machine or switch agents, and that memory doesn't come with you. If it gets corrupted or overwritten, there may be no earlier copy to go back to.
MEMORY.md or equivalent into git or cloud storage on a schedule.uvx fulcra-api file upload MEMORY.md /agents/memory/backup.md
Or install Fulcra's skill library, which includes a memory backup and restore skill, so the agent does this itself:
npx skills add fulcradynamics/agent-skills --skill fulcra-agent-backupuvx fulcra-api file download /agents/memory/backup.md MEMORY.md
MCP clients use read_file instead.uvx fulcra-api file stat /agents/memory/backup.md
uvx fulcra-api file restore <VERSION_ID from file stat>
MCP clients use the restore_file tool.openclaw skills install @fulcra/fulcra-get-started. Fulcra sits beside OpenClaw's own memory, not instead of it. Hermes: Fulcra complements MEMORY.md; keep durable preferences there and changing state in Fulcra.Written by Fulcra. We make one of the tools recommended on this page.