Keep your knowledge safe and portable
Understand where Lore saves entries, how to back them up, and how to move them to another installation.
Lore is coming soon. These guides describe the upcoming release.
Stored locally, outside your projects
Lore uses a local SQLite database for your user account. Global and project-local installations use the same store by default. Uninstalling the package does not remove it.
Keep the active store off network shares and cloud-sync folders. Basic use needs no background service. This release includes no hosted synchronization, model calls, or usage telemetry.
macOS: ~/Library/Application Support/Zedbee/Lore
Linux: $XDG_DATA_HOME/zedbee/lore
or ~/.local/share/zedbee/lore
Windows: %LOCALAPPDATA%/Zedbee/LoreChoose another data location
Use --data-dir for one invocation or ZEDBEE_LORE_DATA_DIR to select another store. The command option takes priority over the environment variable, which takes priority over the default location.
--config selects a settings file; it does not select a database. Ordinary reads do not create missing stores or upgrade their format.
zedbee-lore --data-dir /local/path/lore listBack up this installation
Use the backup command to take a consistent database snapshot. A database backup includes machine-specific project registrations; it is suited to recovering that installation. Save settings.jsonc separately if you also need to recover capture settings.
Restore previews by default. Close active clients before restoring, review the preview, and add --yes only when you are ready to apply it. Lore keeps a pre-restore database backup. Do not copy only a live lore.sqlite file: related transaction files may still contain changes.
zedbee-lore database backup lore-backup.sqlite
zedbee-lore database restore lore-backup.sqlite
zedbee-lore database restore lore-backup.sqlite --yesMove knowledge between installations
Export and import carry project knowledge and revision history without local checkout paths or settings. Export outside the active data directory. The file may contain private project information, so choose its destination carefully.
Unknown source projects need an explicit mapping to registered destination project IDs. Save mappings as an array of objects with from and to IDs. Imports reject conflicting revision histories and preview unless you supply --yes.
zedbee-lore export lore-export.json
zedbee-lore import lore-export.json --mapping mappings.json
zedbee-lore import lore-export.json --mapping mappings.json --yesFollow the reported recovery steps
Run doctor to check the installation. If the store uses a newer format, update Lore instead of trying to repair it with an older version.
If you see STORE_RECOVERY_REQUIRED, close clients and follow the reported recovery-directory instructions. Do not remove files or edit the database by hand while restoring it.
zedbee-lore doctor
zedbee-lore database migrate