Institutional engineering memory for humans and AI agents.
Recallium preserves the decisions, designs, fixes, constraints, rules and working context behind your software, so engineers and AI agents in Claude Code, Codex, Cursor and 60+ tools start from what your team already knows.
with Recallium
on LongMemEval →
Codex
Cursor
VS CodeYour engineering organization forgets every day.
An engineer and an agent spend two hours on a production issue. They learn why an architecture decision exists, find a hidden constraint, reject two tempting fixes and land the safe one. The code keeps the implementation. The judgment usually leaves with the session.
Engineering judgment should not disappear when the conversation ends.
Git says what. Recallium says why.
A commit tells an agent that authentication changed. Recallium tells it why the team changed it, which alternatives were rejected, which constraint drove the call, and what earlier decision it replaced.
commit 7d8f1c3- Why
- The security review found a replay risk in a leaked 30-day token.
- Rejected
- Shorter-lived JWTs on their own: mobile sessions would drop every hour.
- Constraint
- Mobile clients must tolerate 24 hours offline.
- Replaces
- The March token decision, still on record.
Your agents shouldn't follow yesterday's decision.
Engineering knowledge evolves. Recallium keeps the full history and makes the current decision explicit, so an agent that finds the March call also sees what replaced it and why. A stale memory is more dangerous than a missing one.
- MarchUse long-lived JWTs with a 30-day expiryreplaced · still on record
- SeptemberUse rotating refresh tokensReason: the security model changed · commit 7d8f1c3current
What one agent learns, your whole team knows.
Session to session, engineer to engineer, agent to agent, repository to repository. Pro turns what one developer's agent works out into what every teammate's agent starts from, and the knowledge stays with the team when people move on.
The week, in one recap
Every teammate's decisions and fixes across projects, with names attached. Read it instead of calling a status meeting.
Personal until you share it
Keep drafts private, then promote a memory or a whole project to the team when it is ready.
Ask what a teammate decided
“What did Sam decide about auth?” Search by author and get their reasoning, not a Slack archaeology dig.
Knowledge stays when people move on
Shared memory belongs to the team. Hand off a project or an on-call shift with its full history attached.
Models come and go. Institutional memory stays.
Connect once over MCP. Use Claude Code today, Codex tomorrow, a private model where required: Recallium is not Claude's memory, Codex's memory or Cursor's memory. It is your team's, every tool is a client of it, and your engineering knowledge is never trapped inside one vendor's conversation history.
- 01Connect onceOne MCP endpoint in Claude, Cursor, Codex, VS Code and 60+ clients. Nothing to install.
- 02Work as usualDecisions, fixes and patterns are captured as your agents work, with files and reasoning attached.
- 03Every agent remembersAny agent, in any tool, starts from what the team already knows.
Your engineering memory belongs to you.
- We do not train AI models on your memories. We do not sell your data. Period.
- Sharing follows the repository. A memory stays personal until you share it with the team.
- Teams and role-based access on Recallium Cloud: the server decides who reads a project's memory.
- Memory you can inspect, not a black box: see what each project holds and how it connects.
Engineering memory should be ubiquitous, not expensive.
Persistent context should not be rationed by query, repository or conversation. One agent reads the code and records what it learned; every teammate's agent gets it back in one search instead of re-reading the files, so the team pays for those tokens once.
Never make your team relearn what it already knows.
Engineering memory that survives sessions, repositories, people and AI tools. Start free on your own, bring the team onto Pro when you are ready. Recallium Cloud is in a closed pilot; join the waitlist for general availability.