Expand description
Lore - Reasoning history for code
Lore captures the story behind your commits by recording AI-assisted development sessions and linking them to git history.
Git captures code history (what changed). Lore captures reasoning history (how and why it changed through human-AI collaboration).
§Modules
capture- Session capture from AI coding toolsconfig- Configuration managementdaemon- Background daemon for automatic session capturegit- Git repository integration and auto-linkingmcp- MCP (Model Context Protocol) serverstorage- SQLite database operations and data modelssync- Serverless git-ref sync (reasoning history in the user’s repo)
Modules§
- capture
- Session capture from AI coding tools like Claude Code and Copilot. Session capture from AI coding tools.
- config
- Configuration management for Lore settings. Configuration management.
- daemon
- Background daemon for automatic session capture and file watching. Background daemon for automatic session capture.
- git
- Git repository integration for commit linking and auto-detection. Git integration.
- mcp
- MCP (Model Context Protocol) server for exposing Lore data to AI tools. MCP (Model Context Protocol) server for Lore.
- storage
- SQLite storage layer for sessions, messages, and links. Storage layer for Lore.
- summarize
- LLM-powered session summarization. Session summary generation via LLM providers.
- sync
- Serverless git-ref sync for storing reasoning history in the user’s own repo. Serverless git-ref sync for Lore.