Meet Lore
Keep the decisions, discoveries, and gotchas behind your code available to developers and coding agents.
Lore is coming soon. These guides describe the upcoming release.
Keep what you learn
Code shows what a project does. It doesn't always explain why a choice was made, which business rule matters, or what went wrong last time.
Lore gives that knowledge a lasting home. Add an explanation, link the evidence, and make it available when you or your agent returns to the work.
Preserve provider identifiers.
Changing their format can create duplicate imports.
Evidence: test/import.test.tsFind the context for your work
An entry can apply to the whole project, a folder, or a file. Searching by location helps bring back the knowledge that belongs with the code you are changing.
Lore also supports personal entries across projects and entries deliberately shared between selected projects. These all stay in the same local store for your user account.
zedbee-lore list --path src/jobs/
zedbee-lore query "provider identifiers" --path src/jobs/import.tsKeep the explanation and its evidence
Record architecture choices, conventions, business rules, decisions, and gotchas. Evidence can point to a test, a commit, a document, a person, or an investigation.
An entry keeps its revision history. Pending, stale, and disputed labels help you decide what needs another look. A recorded claim still needs judgment; a name in the author field does not prove the claim is correct.
Use Lore with your coding agent
Agents can read and write entries through the command line or an MCP connection. MCP is a way for an agent to use tools supplied by another application.
Lore responds when an entry is submitted or requested. It does not watch every conversation or automatically learn from every session.
Connect your agent