Lore Local
One app with everything included: the server, its own database and local models, and the lore command. Its first run asks how this computer uses Lore and connects the assistants it finds, showing each change first.
Download
Install it, connect your assistants, and they look in Lore first.
Three steps: get Lore for your computer or your team, run lore connect, then ask, or let your assistant consult Lore as it works.
Download LoreComing with 1.0
What you get
One server, and the ways to reach it.
The team server
A container image, a compose file to try it on one machine, and a Helm chart for Kubernetes. It runs anywhere a container does.
The desktop app
The window onto your team's Lore, with an installer for macOS, Windows and Linux.
Connect
Three commands for every assistant on this computer.
The lore command connects Claude Code, Codex, Cursor, Windsurf, GitHub Copilot and other MCP assistants: their MCP entry, Lore's rules in their instructions, and for Claude Code the hooks and the status line.
$ lore connect # shows the plan for every assistant found here, then does exactly that$ lore status # each assistant: connected, connected to another Lore, not connected$ lore doctor # Lore reachable, the token, each connection; what to fix
- Every file is backed up before it changes, and a second connect changes nothing.
- Another Lore's entry is never replaced silently.
- The token lives in the system's keychain, never in a file.
Until 1.0
No public downloads yet, on purpose.
Each release is built and tested by a maintainer, and every security gate must pass before it is tagged. Downloads open here with Lore 1.0.