News · Use case · November 7, 2026
Switch AI, keep your memory: a ten-minute test
Try it yourself: save a memory through one agent, find it in a new session, and share one file with a Ghost ID, all on your own node.
DRIVE 369 DAO · 2 min read
AI assistants are getting better every month, and people switch between them. Each switch usually means starting from zero. When memory lives on your node, an agent is a guest: it can come and go, and your memory stays. Here is a ten-minute test of that claim.
You need a Ghostdrive node and an agent that speaks the Model Context Protocol (MCP), such as Claude Code or Claude Desktop. The setup steps are in this guide.
The test
- Save. In a session, ask your agent to remember something specific: "Remember that the contract renews on 1 March and the notice period is 30 days." The agent calls
ghostdrive_remember, and the note is stored as an encrypted file on your machine. - Close the session. Quit the agent entirely.
- Start a new session. Ask: "What was the notice period in my contract?" The agent calls
ghostdrive_search. The search runs on your CPU, over an index sealed with your vault keys. - Check where it lives. Run
ghostdrive memory. It prints the state of the memory on your node. The note is a file under your repository, encrypted. - Share one file. Ask the agent to send that note to another Ghost ID. It uses
ghostdrive_send. The recipient gets a capability for that one file and can read nothing else.
What this shows
- The memory is yours, not the agent's. Any MCP agent can use it while you allow it, and none holds it when you close it.
- Sharing is narrow. A capability is permission for one file.
- Nothing left the machine except what your network settings already allow.
Limits to know
- This is node and agent software you run yourself, not a one-click app yet.
- PDF and Word extraction stays in the app for now; the node reads text files.
- Search needs
ghostdrive backup on. - The tools list is in the MCP guide; more are planned.