Lore / Docs

Appearance

Requirements and production sources ​

Lore automatically reads repository documentation, merged PR discussions, and GitHub issues. Include issue links in PR descriptions to preserve the connection between requirements and implementation. Review comments retain their affected file and revision. PR bodies retain changed-file lists. Incident reports committed as Markdown in repository documentation are ingested with the other documentation.

Connect Linear ​

  1. Open Settings → Sources in Lore.
  2. Select Linear and the repository the requirements concern.
  3. In Linear, copy the team's UUID and create a read-only API key with access to that team.
  4. Enter the team ID and key in Lore, then select Connect source.
  5. The status changes from pending to ready after the first automatic sync.

Ask your agent: “Before implementing password reset, use Lore with issue AUTH-123 and check the expected behavior and prior fixes.”

Connect Sentry ​

  1. Open Settings → Sources and select Sentry.
  2. Select the affected repository.
  3. Enter the Sentry organization/project slugs, for example acme/accounts-api.
  4. Create a Sentry token with project:read and event:read access to that project.
  5. Enter the token in Lore and connect.

The connector uses hosted Sentry at sentry.io. It retains issue titles, recurrence counts, first/last seen dates, status and culprit location. It does not ingest raw events, customer request payloads, breadcrumbs, or stack-frame local variables.

Ask: “While changing src/auth, check recurring production failures and distinguish confirmed fixes from issues that are only marked resolved.”

Access and freshness ​

These initial connectors are personal: only the connecting Lore member can retrieve that connection's content, and only while authorized for the mapped repository. It is not shared with teammates or included in GitHub replies. Credentials are encrypted. Use a token restricted to the intended source; do not paste it into chat.

Connections reconcile about every 15 minutes, subject to workspace ingestion capacity. Full reconciliation replaces edited content and removes documents no longer returned by the provider. Failed or partial pagination never replaces the prior snapshot. Stale or failed snapshots are withheld from retrieval. Retries use increasing delays. Large sources exceeding 10,000 Linear issues or 20,000 Sentry issues require a narrower source mapping before synchronization can complete.

Disconnecting immediately deletes that connection and its stored documents. To rotate a token, connect the same repository/source/target again with the new credential.

Lore does not require you to review ingested requirements or incident lessons.