Your coding assistant stops forgetting your project.
Claude Code, Cursor, Codex, and Cline remember your architecture, your decisions, and your conventions — across sessions, and across your whole team.
$ npx ultramemory setupTrying a local cache hack on my branch — not sure it stays.
Personal TODO: refactor the parser once the spike lands.
Convention: all dates are UTC ISO-8601 at the boundary.
Decision: the edge gateway owns auth-token validation.
Agreed conventions are promoted to the shared project memory your team's tools read from.
Every new session, your assistant has amnesia.
You paste the same context, re-explain the same conventions, and it still suggests the pattern you banned three weeks ago.
Context resets every session
No more re-explaining the codebase every morning before you can get real work done.
Each teammate’s AI relearns from scratch
What one developer taught their assistant never reaches anyone else’s.
The kinds of things it keeps.
Not the storage mechanism — the project knowledge that actually saves you time.
Architecture decisions ★
The ADRs and the why behind them — so it stops re-litigating settled calls.
Naming & style conventions
Your house rules for names, structure, and formatting, applied every time.
“Don’t do this” gotchas
The patterns you banned and the traps that bit you — remembered, not repeated.
API contracts
The shapes your services agree on, so generated code matches the interface.
Past bug fixes
How a tricky bug was actually solved, ready the next time it resurfaces.
Who owns what
The map of areas and owners, so the assistant points to the right person.
Works in the tools you already use.
Drop it in via MCP (2 tools) or the SDK — no new editor, no workflow change.
// Wire ULTRAMEMORY into an MCP-capable editor (Claude Code, Cursor, Codex).
import { Ultramemory } from "@ultramemory/sdk-ts";
const memory = new Ultramemory({ apiKey: process.env.ULTRAMEMORY_KEY });
// remember a project decision
await memory.remember({
text: "Auth tokens are validated in the edge gateway, never in services.",
scope: "project:checkout",
source: "agent",
});
// recall the relevant slice for the current task (ranked facts, not raw history)
const facts = await memory.recall({
query: "where do we validate auth tokens?",
scope: "project:checkout",
budget: 1200, // token budget — feed the model only what it needs
});MCP · 2 tools — works with
- Claude Code
- Cursor
- Codex
- MCP
- Cline
One shared bucket your whole team reads from.
Your personal experiments stay yours; agreed conventions become team memory automatically — so your teammates' assistants and your CI agents read the same decisions.
Trying a local cache hack on my branch — not sure it stays.
Personal TODO: refactor the parser once the spike lands.
Convention: all dates are UTC ISO-8601 at the boundary.
Decision: the edge gateway owns auth-token validation.
Promotions are governed: who asserted it, the rules it passed, and when it became shared.
This is the on-ramp to teams of agents working together →
Fast, and it won't slow your model down.
Recall in sub-200ms p95, and it feeds the model only the relevant slice — so long sessions don't bloat the context window.
the latency target we hold to, on real project memory
Speed is a maintained SLO, not a guaranteed number. The supporting bars are our own measurements until independent benchmarks land.
How project memory, MCP wiring, and team sharing work →
The technical depth lives in the developer lane — the quickstart, the MCP plugin, and the SDK reference.
Give your editor a memory in 5 minutes.
Free to start, pay for what you use. No new editor, no workflow change.