RecallNest
Shared Memory Layer for Every AI Client — CLI agents, desktop apps, your own scripts
One memory. Every client. Context that survives across windows — and across machines.
A local-first memory system backed by LanceDB that turns scattered conversation history into reusable knowledge — shared across your coding agents, recalled automatically.
English | 简体中文 | Roadmap | Website
Why RecallNest?
Coding agents forget everything between windows. Your context — project configs, debugging decisions, entity mappings — is scattered across Claude Code, Codex, Kimi, Antigravity — and every other terminal you open — with no shared memory.
RecallNest is one LanceDB-backed memory layer that all of them read and write. Context stored in one window is recalled in another. Sessions checkpoint on exit and resume on start. Memory decays, evolves, and self-organizes — it is not a log you grep.
What a recall actually looks like
Query : deploy rollback
Hits : 5
# ID Score Category Tier Source Date Age Retrieval Path
1 ee79037a 46.1% cases peripheral cc 2026-08-25 2d vector
[assistant] Rolled back to the previous image and pinned the digest so the next…
prov : evidence/transcript-ingest
imgs : 52 agent-made in this session · read sess=dca70d4a
