Keep the knowledge behind your code.
Every project has things you only learn by working on it. Lore keeps those decisions, discoveries, and gotchas in reach for you and your coding agents.
Some knowledge never makes it into the code.
Why you chose that approach. The rule a customer depends on. The small change that caused a surprisingly big problem.
Keep decisions, conventions, business rules, and gotchas in one place. Each entry explains what to remember, why it matters, and where it applies.
While fixing customer imports, an agent learns why IDs must stay unchanged. It saves this note for future work.
Keep customer IDs unchanged.
Changing a customer’s ID can make the next import create a duplicate record.
- Where it applies
- Customer imports in
src/jobs/ - Supporting test
test/import.test.ts
The session ends.
The knowledge stays.
Learn it once. Leave a useful explanation.
Your agent shouldn’t have to search Lore just to discover that knowledge exists. Synced project instructions give it a short inventory of what’s available. The full explanations stay in Lore until they’re needed.
Record the discovery
Customer IDs must stay unchanged
Save what the agent learned, why it matters, and the part of the project it applies to. Link the supporting test or investigation.
Make its presence known
A heads-up in project instructions
Sync Lore’s guidance so the agent can see what kinds of knowledge are available for the project or folder, without loading every entry.
Read what matters now
Working on customer imports?
The agent looks up knowledge for that work, then reads the relevant explanations and evidence. Other details stay out of its working context.
Knowledge you can question and update.
Save an explanation alongside its evidence. Review new discoveries, revise an entry as the project changes, and look back through its history.
Entries can be marked as pending, stale, or disputed. That makes it easier to see what needs another look.
See how entries workDiscovery recorded
Changing customer IDs can create duplicate records.
Evidence linked
test/import.test.ts
Explanation updated
Earlier versions stay available to read.
Saved on your computer
Local knowledge. Available to your agent.
Lore saves entries on your computer, outside your project folders. Use it from the command line or connect it to a coding agent through MCP, a standard way for agents to use tools.
Agents submit discoveries and look up context when they need it. Lore doesn’t watch every conversation.
Explore agent integrationKeep what you learn.Build on it next time.
Coming soon
Explore the guides to see how Lore keeps useful knowledge available for your next project session.
Read Lore docs