--local).
It only reads the agents’ own memory folders. It never touches hand-written files like CLAUDE.md, and it never modifies anything inside the agent folders.
Supported sources
| Agent | Location | Unit of capture |
|---|---|---|
| Claude Code | ~/.claude/projects/<project>/memory/ (per project) | one file is one memory |
| GitHub Copilot | VS Code globalStorage/github.copilot-chat/memory-tool/memories/ | one memory per ## section, or the whole file if it has none |
## headings inside a topic file, so each ## section becomes its own memory. A Copilot file with no ## headings is captured as a single memory.
Local vs cloud
By default, capture uploads to the Versuno cloud and needs you logged in (versuno login).
With --local, nothing leaves your machine. Capture writes the same normalized memories to ~/.versuno/memory/ as plain Markdown files. No account, no network, no login. Search them later with versuno memory recall.
Local writes are idempotent. Each memory is keyed on a stable identity, so running capture again skips the memories that haven’t changed and rewrites the ones you edited in place. No duplicates.
Options
| Flag | Description |
|---|---|
--local | Write to the local store (~/.versuno/memory/) instead of the cloud. No account needed. |
--review | Step through each memory and drop any you don’t want before capturing. The default is to capture all. |
--dry-run | Print the normalized payload as JSON instead of capturing. Works without logging in. |
How it works
- Find every installed agent’s memory folder.
- All folders start selected. Press space to skip any, then enter.
- Normalize each folder’s memories into one shape: content, title, summary, type hint, wikilinks, content hash.
- Save them. Upload to the cloud, or write to the local store with
--local.
Local store layout
Examples
See also
- versuno memory recall searches the local store
- versuno memory install-hook makes Claude Code recall automatically

