Lore – Give your coding agent the decisions your team made
Quickstart · How it compares · How it works · Docs · CLI · Changelog
Give your coding agent the decisions your team already made — so it stops re-doing things you ruled out.
Lore keeps your team's recorded knowledge — requirements, decisions, designs, roadmaps, and prompts — as typed Markdown in your repo and serves it read-only to Claude Code, Cursor, and Claude Desktop over MCP, so the agent cites your decisions instead of violating them. No RAG, no embeddings, no model call to decide what's relevant — retrieval is deterministic and reproducible. It is built on RAC — Requirements as Code , the open-source engine underneath; the package, CLI, and MCP server ship under the rac name.
Lore isn't a search index or a memory tool — it's the deterministic system of record an agent grounds against. Fuzzy retrieval (RAG, agent memory) is good at finding what's near a loose question; Lore is good at returning the exact, current decision and declining the ones you've superseded. They compose well — recall fuzzily, then verify in Lore.
Scaffold identity and your first artifact:
Connect your agent (Claude Code, from your repo root):