Entries with owners
How-tos, rules, decisions and incidents, each with a named owner, approved before it counts, and marked when it may no longer be true.
Your team's knowledge, where your assistants look first
The decisions, runbooks and hard-won rules that live in people's heads, written down once, each with an owner and a date it was last checked. Before Claude Code, Codex or Cursor starts a task, Lore hands it the few entries that matter, and it cites them so you can check.
24/24 right answers for Claude with Lore, 16/24 from a docs folder−36% tokens per run
Until 1.0, a maintainer builds each release by hand.
How it works
How-tos, rules, decisions and incidents, each with a named owner, approved before it counts, and marked when it may no longer be true.
Before it opens a file, your assistant hands Lore its task: Claude Code, Codex, Cursor, Windsurf and GitHub Copilot, or any assistant that speaks MCP.
The few passages that answer the task, with where each came from, so the assistant cites them and you can check.
Measured on 25 October 2026
The same team knowledge given to the same assistants two ways: as a docs folder, and through Lore.
Where your data lives
Lore runs where you put it. Your entries live in its database on that machine, and an assistant gets the passages for its task, not the whole base.
One app with everything in it: the server, its own database and its local models.
The same server in a container, on a machine your team runs, with access rules per area of knowledge.
Download
lore connect, and your assistants look in Lore first.The app for macOS, Windows and Linux, or the server image for your team. Downloads open with 1.0.