Lore Context

Lore Context

The control plane for AI-agent memory, eval, and governance.

Know what every agent remembered, used, and should forget — before memory becomes production risk.

Getting Started · Website Quickstart · Benchmark Methodology · API Reference · Architecture · Project Plan · Release Status · Roadmap · Integrations · Deployment · Changelog

🌐 Read this in your language: English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Tiếng Việt · Español · Português · Русский · Türkçe · Deutsch · Français · Italiano · Ελληνικά · Polski · Українська · Bahasa Indonesia

Localized docs may lag the current English release notes; the canonical v2.1 docs are the English README and docs/ set.

---

What is Lore Context

Lore Context is an open-core control plane for AI-agent memory: it composes context across memory, search, repository graphs, and tool traces; evaluates retrieval quality on your own datasets; routes governance review for sensitive content; and exports memory as a portable interchange format you can move between backends.

It does not try to be another memory database. The unique value is what sits on top of memory:

• Context Query — single endpoint composes memory + web + repo + tool traces, returns a graded context block with provenance.
• Memory Eval — runs Recall@K, Precision@K, MRR, stale-hit-rate, p95 latency on datasets you own; persists runs and diffs them for regression detection.
• Governance Review — six-state lifecycle (candidate / active / flagged / redacted / superseded / deleted), risk-tag scanning, poisoning heuristics, immutable audit log.
• MIF-like Portability — JSON + Markdown export/import preserving provenance / validity / confidence / source_refs / supersedes / contradicts. Works as a migration format between memory backends.
• Repo Graph — deterministic repository indexing (files, symbols, imports, calls, routes, tests) exposed as API routes and read-only MCP tools so agents ground repository answers in a stable project-context contract.
• Multi-Agent Adapter — first-class agentmemory integration with version probe + degraded-mode fallback; clean adapter contract for additional runtimes.

When to use it

Quick Start

# 1. Clone + install

git clone https://github.com/Lore-Context/lore-context.git cd lore-context && pnpm install

2. Run the quickstart helper and inspect the activation report

pnpm quickstart -- --dry-run --activation-report

3. Generate a real API key (do not use placeholders in any environment beyond local-only dev)

export LORE_API_KEY=$(openssl rand -hex 32)

4. Start the API (file-backed, no Postgres required)

pnpm build && PORT=3000 LORE_STORE_PATH=./data/lore-store.json pnpm start:api

5. Write a memory

curl -H "Authorization: Bearer $LORE_API_KEY" -H "Content-Type: application/json" \ -X POST http://127.0.0.1:3000/v1/memory/write \ -d '{"content":"Use RDS as truth store and Qdrant as the derived recall index for Lore Context production.","memory_type":"project_rule","project_id":"demo"}'

6. Query context, then inspect the returned traceId in the Evidence Ledger

curl -H "Authorization: Bearer $LORE_API_KEY" -H "Content-Type: application/json" \ -X POST http://127.0.0.1:3000/v1/context/query \ -d '{"query":"production storage","project_id":"demo","token_budget":1200}'

For the public website quickstart, see lorecontext.com/quickstart. For full setup (Postgres, Docker Compose, Dashboard, MCP integration), see docs/getting-started.md.

The canonical alpha quickstart is git clone + pnpm quickstart. Lore does not currently publish or claim a public @lore-context/quickstart npm package. The MCP stdio server is published separately as @lore-context/server for registry and client distribution, and the SDK middleware ships as @lore-context/sdk-middleware (npm) and lore-context-middleware (PyPI).

For AI-readable discovery, the website publishes /llms.txt and /llms-full.txt from public documentation only. The Official MCP Registry entry is published, and additional distribution drafts live under docs/distribution. Launch drafts live under docs/launch, and design partner intake under docs/design-partners. The public benchmark page is a reproducible methodology and small smoke-run report, not a competitive benchmark-win claim.

Architecture

The diagram below shows the full open-core plus hosted-production shape. In the public OSS repo, local file/Postgres deployment is supported directly; hosted Google sign-in, AWS SQS workers, private embeddings, billing, and multi-tenant operations are commercial hosted-cloud surfaces.

                       ┌───────────────────────────────────────────────┐

MCP/REST clients ─► │ apps/api (auth + rate limit + evidence) │ (Claude Code, │ ├── Memory Inbox / lifecycle / audit │ Codex, Cursor, │ ├── capture ingestion + recall hydration │ OpenCode...) │ ├── context query (memory/web/repo/traces) │ │ ├── repo graph query / symbol / impact │ │ ├── Google sign-in + hosted MCP metadata │ │ └── OpenAPI + usage + operator surfaces │ └───────────────┬───────────────────────────────┘ │ capture / embedding / graph jobs ▼ ┌───────────────────────────────────────────────┐ │ memory-worker (AWS SQS + DLQ fan-out) │ │ ├── auto redaction / curation / save │ │ ├── dreaming butler (prune/merge/resolve) │ │ ├── private Qwen3 embedding service │ │ └── Qdrant dense+sparse indexing │ └───────────────┬───────────────────────────────┘ │ ┌────────────────────┼────────────────────┐ ▼ ▼ ▼ RDS PostgreSQL 16 Qdrant derived index apps/dashboard truth store + audit lore_memories_v12 user-facing SaaS

For detail, see docs/architecture.md.

What's in v2.1.0

v2.1.0 is the Repo Graph API and MCP Tools release. It makes Lore's own repository graph a first-class agent memory surface: deterministic TypeScript/JavaScript repository indexing for files, symbols, imports, calls, routes, tests, and process hints, exposed through API routes and read-only MCP tools so agents ground repository answers in a stable project-context contract instead of ad hoc text search.

v2.1.0 is the current open-core source line. The hosted Lore Cloud production line also runs v2.1.0 on the commercial AWS/Qdrant/private-embedding substrate, but hosted operations, billing, production release automation, and Secret Vault runtime stay in Lore-Context/lore-cloud.

| Governance state machine + audit log | ✅ OSS + hosted production | `packages/g