Lore

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

Lore saves all your AI coding sessions from Claude Code, Codex, etc and links them to commits. When you look at code later, you can see the conversation that produced it.

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

Arch Linux (AUR)

yay -S lore-cli-bin

Or with any AUR helper. See lore-cli-bin.

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

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:

• Installation
• Quick Start
• Command Reference
• Guides
• FAQ

Data Location

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

All data stays on your machine.

Contributing

See CONTRIBUTING.md.