Open Case →
MEMORY ACTIVE · COGNEE GRAPH ONLINE

Your codebase
remembers.
Finally.

Every commit hides a decision. Every PR buries a reason. Lore gives your codebase a persistent memory — so you can interrogate the past, any time, forever.

Open a Case →How it works
CASE FILE#0042
MEMORY ACTIVE
Repositoryvercel/next.js
Query

"Why did we switch from Webpack to Turbopack in 2023?"

The migration was triggered by build time complaints across 47 open issues. Benchmarks in PR #51203 confirmed 10x faster cold starts. Decision authored by @timneutkens in RFC Sept 14, 2023.

Evidence
issue #42847PR #51203commit a3f9b2cRFC Sept 2023
∞
Sessions remembered
4
Memory operations
Any
Public GitHub repo
0
Context lost
// The Process

Three steps. Total recall.

01
Point Lore at your repo

Paste any public GitHub URL. Lore ingests every commit, PR, issue, and comment — the full institutional history of your codebase.

await cognee.remember(repo_url)
02
Cognee builds the graph

History is structured into a hybrid graph-vector knowledge graph. Relationships between decisions, contributors, and code are permanently mapped.

graph + vector → knowledge
03
Query forever

Ask anything about your codebase's past. Memory persists across infinite sessions — context never dies, every answer cites its sources.

await cognee.recall(question)
// Memory Lifecycle

Four operations.
Nothing forgotten.

remember()
remember()

Ingest commits, PRs, and issues into the knowledge graph. Every decision, permanently mapped.

recall()
recall()

Ask anything. Cognee routes between semantic search and graph traversal to surface the right answer.

improve()
improve()

Enrich memory after new commits. Prune stale nodes. The graph sharpens as your codebase grows.

forget()
forget()

Surgically remove deprecated branches or outdated context from persistent memory.

// Open a Case · Free · No Setup

What does your
codebase know?

Paste a GitHub URL. Lore handles the rest.

Open a Case →