Lore

Reasoning history for code. Lore captures AI coding sessions and links them to git commits.

Git captures what changed, Lore captures why it changed. The prompts, approaches, and decisions from your AI conversations.

Documentation: lore.varalys.com

Use Cases

Code review: See the AI conversation that produced a PR, not just the diff
Debugging: Understand why code was written a certain way
Knowledge transfer: AI conversations stay with the code when people leave
Search: Find that conversation where you solved a similar problem

Installation

Homebrew (macOS)

brew install varalys/tap/lore

From crates.io

cargo install lore-cli

From Releases

Download from GitHub Releases.

Quick Start

# Guided setup
lore init

# Import existing sessions
lore import

# List sessions
lore sessions

# View a session
lore show abc123

# Link to current commit
lore link abc123

# Find sessions for a commit
lore show --commit HEAD

# Trace a line of code to its AI session
lore blame src/main.rs:42

# Search across all sessions
lore search "authentication"

Key Features

Feature	Description
Session Capture	Import from 10+ AI coding tools
Git Linking	Connect sessions to commits
Full-text Search	Find any conversation
Blame Integration	Trace code to sessions
MCP Server	Let AI tools query your history
Background Daemon	Real-time capture

Supported Tools

Claude Code, Codex CLI, Gemini CLI, Amp, Aider, Continue.dev, Cline, Roo Code, Kilo Code, OpenCode

See Supported Tools for details.

MCP Integration

Let Claude Code query your session history:

claude mcp add lore -- lore mcp serve

Claude can then search sessions, retrieve context, and continue where you left off.

See MCP Guide for setup details.

Documentation

Full documentation at lore.varalys.com:

Data Location

~/.lore/
├── lore.db       # SQLite database
├── config.yaml   # Configuration
└── logs/         # Daemon logs

All data stays on your machine.

Contributing

See CONTRIBUTING.md.

lore-cli 0.1.6