← Back to Discover

CommitLore

A Git-based memory for coding agents that keeps constraints and ruled-out approaches beside the code and hands an agent only the records that still apply to the file it is about to edit.

Command-line toolsMCP servers
Visit website ↗

What it does

CommitLore targets a gap between code and judgement: a team rejects an agent's idea for a non-obvious reason, the code keeps the outcome but not the reason, and a later agent proposes the same idea again. The tool records constraints, rejected alternatives and warnings next to the code, as Git trailers or notes rather than in a hosted memory service. SQLite is used only as an index that can be rebuilt. A captured record is verified against the conversation with the agent and the changes staged for commit. Each record has a lifecycle (active, superseded or expired), and before an edit the tool returns only the active records for that path, graded as directives, claims or withheld content. Delivery gives the agent context; it does not block the edit. It works as a plugin for Claude Code and Codex, and registers over MCP for hosts such as Gemini CLI, Cursor, Windsurf and opencode. A Hermes integration is also listed. Installation is a shell or PowerShell script and needs Node.js and Git. The repository is MIT licensed, and a GitHub Action carries records through squash merges.

Capabilities

  • Stores decisions in Git trailers and notes, with no hosted memory
  • Verifies captured records against the agent session and staged changes
  • Tracks active, superseded and expired decisions
  • Delivers only the records that apply to the path being edited
  • Plugins for Claude Code and Codex, MCP for other agent hosts
  • GitHub Action keeps records through squash merges

When to use it

  • Coding agents keep re-proposing ideas your team has already ruled out
  • You want design decisions to live in the repository history
  • You use Claude Code, Codex, Cursor or similar agents on a shared repository