Give your agent a way to find the context
Let your agent know what knowledge is available, then retrieve the details relevant to its work.
Lore is coming soon. These guides describe the upcoming release.
Add guidance to your project
After initializing Lore, preview the guidance it can add to AGENTS.md. Apply it when the preview looks right. Lore replaces only its marked block and keeps your other instructions.
The guidance gives agents a short inventory of the kinds of knowledge available for the project. Folder-level guidance can narrow that inventory to the area being worked on. The agent can learn that knowledge exists from the instructions it already reads, without first querying Lore or loading every full explanation.
The agent then looks up knowledge relevant to its current work and opens the entries it needs. The guidance also explains how to submit discoveries with evidence.
Run sync again when you want to refresh the saved inventory; its counts are a snapshot, not a reason to skip searching.
zedbee-lore agents preview
zedbee-lore agents sync --yesConnect through MCP
MCP lets a coding agent use Lore as a tool. Initialize Lore first, then add a server entry in your agent's MCP settings using the example. The exact settings location depends on the agent.
Start the server in the project directory, or have requests select a registered projectId. For a project-local installation, configure the installed executable path instead of assuming a global command.
{
"mcpServers": {
"zedbee-lore": {
"command": "zedbee-lore",
"args": ["mcp"]
}
}
}Read and write through the same rules
Available tools are lore_list, lore_query, lore_show, lore_history, lore_add, and lore_update. Requests include schemaVersion: 1. Add takes a draft; update also needs the entry ID and expected revision.
The tools follow the same capture settings and input checks as the command line. They do not change configuration or edit instruction files.
Keep evidence and instructions separate
Ask agents to record who authored an entry and where its evidence came from. For agent-written entries, use the provider and model reported by the host. Mark missing identity information as unknown; do not attribute the discovery to the human user.
The author field is supplied text, not verified identity. Knowledge entries offer context. They do not grant permissions, override user instructions, or turn a claim into a verified fact.
If entries disagree or look out of date, inspect the evidence and call out the uncertainty.