Find what belongs with the code
Search by topic, project, or location, then read the explanation and evidence.
Lore is coming soon. These guides describe the upcoming release.
Start with the area you are changing
Use list to browse or query to search. Paths are relative to the project root, even when you run the command from a nested folder.
A file inherits knowledge recorded for the project and its parent folders. A folder search also includes knowledge for locations inside it.
zedbee-lore list --path src/jobs/
zedbee-lore query "provider identifiers" --path src/jobs/import.ts
zedbee-lore list --type gotchaCheck whether the entry still applies
Ordinary results include active, stale, and disputed entries, with their states shown. Stale or disputed knowledge may still be useful, but check it before relying on it.
Pending and retired entries appear only when you request those states. Use the entry ID to read its full explanation, evidence, and history.
zedbee-lore list --state pending
zedbee-lore show ENTRY_ID
zedbee-lore history ENTRY_IDUse the right project
Linked Git worktrees share a project identity. Separate clones need to be attached explicitly with projects attach. Personal knowledge applies across projects; shared knowledge applies to its selected projects.
--all-projects searches your registered projects. Use it without a project or path filter. Sharing here means retrieval in the same user's local store, not a hosted team service.
zedbee-lore projects list
zedbee-lore projects attach PROJECT_ID
zedbee-lore query "shared contract" --all-projectsRead another page of results
The default limit is 20 entries; you can request from 1 to 100. JSON results include hasMore and nextCursor. Use the returned cursor with the same filters for the next page.
If the knowledge changes and the cursor expires, restart the search without it. Search words are treated as literal terms.
zedbee-lore query "provider identifiers" --limit 20 --format json