Captures the why at every commit. Shared with your team over plain git — on your machine, not someone else's cloud.
The gap
Attached to the commit — not archived somewhere else.
Team
Shared over plain git — no memory server. Push on commit; sync when you want team context. Ranking adapts personally on your machine — the citation graph stays local and never rides the wire.
01
Sessions ride rekal/<email> — never touch product history or PRs.
02
Dead-ends stay local. What lands on main is what the team inherits.
03
Fetch teammates' branches and fold their sessions into your local store.
Benchmarks
Compression & store
Soul
The trade we make on purpose — one immutable ledger, lazy inference, real reasoning on demand.
Belief · agent first
SOUL.md →Every decision about output format, query interface, and context loading puts the agent first. A compact digest — verdict, confidence, drill pointers — built to act on. Silence when memory isn't the tool. Humans benefit as a side effect.
Lazy inference
No write-time summaries. Retrieval, ranking, routing, and the agent's judgment run over the real record when you ask — compute on demand, nothing derived that can rot. The ask itself becomes another session: distilled and reasoned, riding git with the team — so the cost of that inference is implicitly cached for the next recall.
Zero maintenance
Raw sessions are the truth. The index is a disposable accelerator — rebuild reconciles it. No consolidation pipeline, no memory tiers, no drift.
Personalised ranking
Your machine tracks which sessions you reach. Load-bearing memories get a usage hint and a gentle boost — private, never synced, inert until you build a history.
vs Mem0
Extracts and maintains distilled “memories.”
RekalAppend-only raw ledger. The agent drills the real turns — no lossy distillation to babysit.
vs Tiered memory
L1/L2/L3 and wiki-style compiles (AdaMem, Tencent-style layers) need consolidation to stay fresh.
RekalNo memory layers. Query-time structure over a disposable index — the maintenance problem we exit.
vs Memory SaaS
Another service, another store, privacy and ops on the critical path.
RekalLocal binary. Intent rides git. Nothing to operate.
Install
❯ cd your-project
❯ rekal init
# done
FAQ
Mem0 maintains distilled memories. Rekal keeps a raw append-only ledger and runs lazy inference at ask-time — zero memory tiers to maintain, agent-first digests instead of prose dumps.
Claude Code, Codex, Gemini, OpenCode, Kiro — captured at commit. Also works with Cursor and Copilot. Agent-agnostic: switch tools without losing team memory.
Orphan branches per author. Only merged work reaches the wire. rekal sync folds teammates' sessions into your local index.
No cloud memory API. It rides git on your remote — same push/fetch you already use. No telemetry.
rekal "<problem>" returns scored seeds with confidence — drill, follow a pointer, or stay silent. A personalised recall graph (local-only) adapts ranking to what you reach most — never synced to the team.
No accounts. No telemetry. The CLI is the product.