Lore
Keeper of the Chronicle
The spellbook for your codebase: chronicle decisions, context, and lessons your AI companions can actually read.
โฆ What is Lore?
AI coding tools are stateless. They do not remember why you chose PostgreSQL over SQLite, which safety rules cannot be bypassed, or what tradeoffs already shaped this codebase.
Lore fixes that. It is a local AI memory system for software projects. You capture knowledge once as plain files alongside your code, then export it into instruction files your tools can read automatically.
No external database. No API keys. No cloud sync. Everything lives in .lore/ next to your repo.
โ The Three Artefacts
Spell
A single piece of knowledge: a decision, a fact, a hard-won lesson, or a preference worth preserving.
Tome
A named collection of spells. Default tomes include decisions, facts, preferences, and summaries.
Relic
A raw artifact saved as-is for later distillation. Use relics when things are moving too fast to curate carefully in the moment.
โง How the Magic Flows
โถ First Invocation
Start with onboarding. Lore walks through store setup, your first memory entry, and export flow in one guided ritual.
- Initialize the spellbook with a project description and local defaults.
- Record real knowledge as decisions, facts, preferences, or summaries.
- Export the chronicle so every supported AI tool inherits the same context.
- Enable semantic search later with
lore setup semanticif you want dense embeddings.
โ Start Here
๐ Incantations
Install via pip
Local development
Cast your first spells
๐ Grimoire of Commands
lore onboard, lore init, lore add, lore list, lore remove
lore search <query>, lore index rebuild, lore setup semantic
lore relic capture, lore relic list, lore relic view, lore relic distill
lore export, lore export --format prompt, lore config <key> <value>