A little practice.
A longer memory.
Get a feel for Lore before you install it. These hands-on examples use fictional memories to make the everyday Pi workflow tangible.
Pick up where you left off.
Save a preference with lore_save, leave the conversation, and retrieve it with lore_recall. The conversation changes; your saved memory doesn’t.
- 1. Save a preference
- 2. Start a new session
- 3. Recall it
Pi Session 01
Ready to rememberEdit this sample preference, then save it for the fictional demo/orchard project.
What preferences have I saved for this project?
The earlier message isn’t in this conversation. Lore’s saved memory is.Nothing saved yet. Give this session something worth keeping.
Lore’s memory
0 notesYour saved preference will appear here.
See the Pi tool call
No tool call yet.Some notes belong to a project.
Switch the active repository. In this example, project notes stay with their project, while a global preference can travel with you.
The example memory store
A match without the same words.
Local embeddings can find relevant memories beyond keywords. Compare the example candidates, then see what remains if the local model becomes unavailable.
Lexical candidates
The words match.
Additional semantic candidates
The meaning can match, too.
In Pi, explicit recall combines semantic matches with deterministic recall. Its recent-memory fallback and optional query expansion add behavior beyond this illustration.
Make it part of your day.
Install Lore in Pi and start building a memory of your own.
Start with PiUsing Copilot CLI?