Repositories and memory

Lore extracts useful context from repository notes and GitHub history, including comments, memory files, documentation, architecture decisions, and discussions.

Review facts and evidence

Use Memory to filter by repository or fact type. Open a fact to see the claim and supporting evidence. Treat extracted claims as reviewable summaries, not guarantees: classification can be wrong or become outdated.

Users with repository write access can correct claims and tags or retire facts. Retiring a fact removes it from ordinary retrieval while preserving its history.

Cleanup pull requests

Eligible source-note changes are proposed in a cleanup PR. Lore keeps one open cleanup PR per repository and can add future findings to it. Review the diff before merging. Auto-merge is optional.

Documentation, ADRs, and GitHub discussions can provide evidence without being rewritten. No eligible source changes means no cleanup PR is needed.

Processing and plans

Scans run through a job queue. Free uses low-priority processing, Team uses standard processing, and Business receives priority processing. See the current plans and pricing.

The Free plan permits five active repositories and one seat. Paid plans allow unlimited repositories. Read quotas are shared by the organization, rather than multiplied by its number of seats.

Agent contributions

Ask agents to call record when they discover a durable decision or gotcha. Include a repository-relative path when the context applies to a specific file. Use forget to retire a fact that no longer applies, with a reason explaining why.