Get started with Lore

Connect a repository and your coding agent. Lore ingests the repository and keeps its memory current automatically.

You will need a GitHub account, access to a repository, and a coding agent that can connect to Lore. You do not need to run a server or supply your own AI API keys to use the hosted product.

A repository is a project's collection of files and change history on GitHub. A fact is a piece of knowledge Lore keeps about that project, such as why a particular design was chosen or which mistake to avoid.

1. Connect GitHub

Open Lore and sign in with GitHub. Install the Lore GitHub App and select the repositories you want it to scan. An organization owner may need to approve the installation.

The GitHub App's installation grants Lore access to selected repositories. Your own GitHub permissions determine which of those repositories you can use in Lore.

For example, suppose your team has acme/website and acme/payments. Installing Lore on acme/website does not also connect acme/payments. You can add more repositories to the installation later.

Expected result: your selected repository appears in Lore's Repositories page. If it does not, check the selected GitHub installation and your repository access.

2. Lore ingests automatically

There is no review queue or manual import to complete. Lore starts scanning the repositories you connected and makes extracted context available to your agents. You can check progress in Repositories, but you do not have to keep the page open.

For example, a comment explaining that payment retries must reuse the original request ID can become context your agent retrieves while working on payments. Memory includes evidence links if you ever want to inspect its source.

Expected result: the initial scan finishes and extracted facts become available. A repository with no eligible notes can have an empty result without a failed connection. A cleanup PR, when enabled, is separate from using Lore; merging one is not an onboarding requirement.

3. Connect an agent

Copy the agent setup prompt into your coding agent to have it configure Lore and check the connection. You can also open Agent setup in the dashboard or use the manual instructions on that page. Complete browser authorization when prompted. If your organization requires SSO, complete that sign-in too.

Ask your agent:

Use Lore to list the repositories I can access.

Then:

Use Lore to get the context for owner/repository before making changes.

Replace owner/repository with a repository returned by list_repos. A successful dashboard connection check is useful, but also verify a real tool call from your agent.

Expected result: the agent shows your repository and can read its memory. If the repository appears but has no facts, first check whether its scan has finished.

4. Keep working as usual

Lore keeps connected repositories in sync in the background. Your agent can use that context as you work; you do not need to maintain a review queue. Inspecting, editing, or retiring memory is optional and follows your repository permissions.

For inviting teammates or connecting another GitHub account, see Workspaces and teammates.

Your first successful setup

You have completed setup when all four of these are true:

• You can sign in to the dashboard.
• Your selected repository appears and its scan completes.
• Your agent can call list_repos and see that repository.
• Your agent can call get_context for it, even if the result currently contains no facts.

You do not need to merge a cleanup PR to prove that your agent can connect.