Lore

Lore

Lore keeps a local, searchable archive of your Claude Code and Codex sessions.
It gives coding agents long-term memory in a vault of plain markdown notes that you review.
It checks the skill folders your agents load for duplicates, drift, and broken references.

Three rules hold the design together.

- The vault is the truth. The index, the archive, and anything an agent sees are derived and rebuildable.
- Agents only propose. A person accepts. Agents never get delete.
- Every recalled note says whether the code it points at still matches. A stale note is labelled, not silently served.

Install

Lore is early. There is no signed build. The newest GitHub release, v0.1.1, predates the current code, so build from source. You need Rust. rust-toolchain.toml pins the toolchain, and rustup selects it.

Put target/release/lorectl on your PATH. The examples below assume it is there. lorectl help mem prints the memory commands alone.

The desktop app is a second front end over the same archive. It needs Node.js 20, the Xcode command-line tools, and the Tauri 2 prerequisites for macOS. Run it with npm run tauri dev.

The archive

lorectl scan reads the session logs Claude Code and Codex already keep on disk. It looks in ~/.claude/projects, ~/.codex/sessions, and ~/.codex/archived_sessions. CLAUDE_CONFIG_DIR and CODEX_HOME move those roots. Lore opens them read only and never changes them. A second scan of unchanged files ingests nothing. Every scan ingests the newest files first.

A large history takes a while to scan the first time. lorectl scan --since 30d ingests only the files modified in the last 30 days (h for hours and m for minutes work too), so you can start with recent work and run a full lorectl scan later. A --since scan never marks older files missing.

The…