Project memory that survives the session
Return to a project after three weeks and start warm, not cold.
Without memory
Side projects die in the gap between sessions. You come back after three weeks and spend the first hour re-reading your own code, re-discovering what you decided, and re-attempting approaches you already know fail — you just don’t remember failing at them.
With Rekall
With a project hive, every session starts with injected context: where the project stands, what was decided and why, what is half-finished, and which dead ends are already mapped.
How it works
Create a project hive
A hive scopes memory to the project — episodes and decisions live together. Task and artifact tracking is an opt-in beta (Project Hives), enabled per deployment.
Work normally
Editor hooks capture progress ambiently; session consolidation distills each session into durable episodic and semantic memory.
Come back anytime
Session start injects the project state. “Where did we leave the billing refactor?” gets a real answer, not a shrug.
See it in action
import Rekall from '@rekall/agent-sdk'const rekall = new Rekall({ apiKey: 'rk_...' })// A new session starts with real project stateconst context = await rekall.memories.search({query: 'Where did we leave the billing refactor?',})// → the decision to split invoices, the half-done webhook// handler, and the two approaches that already failed