lore-cli 0.1.9

Capture AI coding sessions and link them to git commits
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127

# Lore

[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
[![CI](https://github.com/varalys/lore/actions/workflows/ci.yml/badge.svg)](https://github.com/varalys/lore/actions/workflows/ci.yml)
[![Release](https://img.shields.io/github/v/release/varalys/lore)](https://github.com/varalys/lore/releases)
![Platform](https://img.shields.io/badge/platform-linux%20%7C%20macOS%20%7C%20WSL2-blue)

**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](https://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)

```bash
brew install varalys/tap/lore
```

### Arch Linux (AUR)

```bash
yay -S lore-cli-bin
```

Or with any AUR helper. See [lore-cli-bin](https://aur.archlinux.org/packages/lore-cli-bin).

### From crates.io

```bash
cargo install lore-cli
```

### From Releases

Download from [GitHub Releases](https://github.com/varalys/lore/releases).

## Quick Start

```bash
# 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](https://lore.varalys.com/reference/supported-tools/) for details.

## MCP Integration

Let Claude Code query your session history:

```bash
claude mcp add lore -- lore mcp serve
```

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

See [MCP Guide](https://lore.varalys.com/guides/mcp/) for setup details.

## Documentation

Full documentation at **[lore.varalys.com](https://lore.varalys.com)**:

- [Installation](https://lore.varalys.com/getting-started/installation/)
- [Quick Start](https://lore.varalys.com/getting-started/quick-start/)
- [Command Reference](https://lore.varalys.com/commands/)
- [Guides](https://lore.varalys.com/guides/linking/)
- [FAQ](https://lore.varalys.com/about/faq/)

## Data Location

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

All data stays on your machine.

## Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md).