An example memory
“We’re on Postgres. No ORM — raw SQL only.”
you typed this once, in whichever tool was open.
01 For the AI tools you already use
The memory layer
that sits under
your AI tools.
Connect once with one key. Itsuki extracts structured memories from any of 26 connected tools and serves them back across all the rest.
Open source · One key, two minutes · Free during early access
connect
{
"mcpServers": {
"itsuki": {
"url": "PASTE_THE_PRIVATE_URL_CREATED_IN_ITSUKI"
}
}
}→ recalled in Cursor — “raw SQL only, no ORM”, saved from Claude Code on Monday
npm install itsukipip install itsuki
One key · 26 tools — assistants, coding agents, workflows
02 One memory, every tool
Tell Claude Code.
Cursor already knows.
One store sits under all twenty-six. Type the fact once, in whichever tool happens to be open, and the next tool to ask gets it back — no export, no re-paste, no second store to keep in sync.
Typed once, in Claude Code
SDKs & API
Python SDK
TypeScript SDK
REST API
AI assistants
Claude
ChatGPT
Coding agents
Claude Code
Codex
Cursor
OpenCode
Antigravity
Agent harnesses
OpenClaw
Hermes
Pi
Agent frameworks
LangChain
CrewAI
AutoGen
Agno
LlamaIndex
Mastra
Vercel AI
CAMEL
Google ADK
OpenAI Agents
Workflow automation
n8n
Dify
Convex
03 The difference
Memory
you can check.
Everyone else replays the transcript and hopes the model finds the point. Itsuki keeps the point, the exact words it came from, and the shape of what it connects to.
- 18
- turns of conversation in
- 4
- durable objects out
- 14
- lines deliberately discarded
- 1
- source every object points to
replayed in full
“hey are we still on for the review” “let me check the calendar one sec” “ok so september is completely packed” “we're moving the pricing review to october” “who's calling it?” “the growth lead owns it now” “cool, i'll tell the team” “thanks!”
+ 10 more turns of the same, replayed on every request.
and source-linked
FactPricing review moves to October.Current · revision 04 · earlier versions restorable
EventReview rescheduled — 12 AugDated, so “when did this change?” has an answer
EntityGrowth lead — personRecalled whenever they come up again
RelationshipPricing review → owned by → Growth leadLets recall follow the graph, not just keywords
Discarded on purpose: greetings, scheduling chatter, and questions with no durable answer. Your rules decide what never becomes memory.
Six months later
“Who moved the pricing review, and when?”
fact pricing review → Octoberevent rescheduled 12 Augentity growth leadsource planning call
A worked example. Every memory stays linked to the words it came from — your agent receives four typed objects and a source it can cite, not eighteen turns to re-read and guess at.
04 How it works
How Itsuki
remembers.
Four moves. One living memory.
01 / Capture
Bring in the moments worth remembering.
Conversations, documents, and events enter through one consistent memory API.
Input
“The pricing review moved from September to October.”
Conversation · Document · EventResult
Input accepted · ready to structure
Scope attached05 One memory layer
Memory across
the entire stack.
Make every product interaction feel continuous.
Build personalization, support, and adaptive experiences from durable user context.
Product memoryContinue the conversation without starting over.
Carry preferences, decisions, and important history across sessions and channels.
Conversational continuityGive planning and tools a reliable working context.
Recall the right facts and relationships without flooding the prompt with history.
Agent contextLet automation learn from what happened before.
Share structured memory across queues, jobs, n8n workflows, and backend services.
Operational memory06 Trust & control
Your memory,
actually yours.
Move fast without turning memory into a black box.
The Itsuki principle- Delete actually deletes
- One pass removes the memory from recall, export and the graph, and clears its vectors and sources — and repeating it converges rather than finding more. Rows are tombstoned first and purged by the space or retention sweep, so nothing deleted is ever served again.
- Every write leaves a receipt
- An audit trail records what was saved, where it came from, and why — open to inspection any time.
- Versioned and reversible
- Updates keep history. Any memory rolls back to any earlier revision, and your memory space exports as JSON.
- No training on your data
- Your memories personalize your tools. They never train anyone’s models.
07 Open architecture
Read the system
before you trust it.
Read the extraction engine. Read the admission rules that decide what becomes memory. Read the delete path. The engine, the SDKs and the schema history are published under Apache 2.0 — memory infrastructure you cannot inspect is just another black box. Publication runs behind deployment: the hosted service is built from a development line, so the newest modules and migrations reach the repository later.
- Apache 2.0Permissive license, commercial use included.
- Schema historyThe migration history is published in order, not a single snapshot drop — and it lags the deployed service.
- No lock-inExport one memory space — its memories, receipts, rules and revision history — as JSON at any time.
08 / BeginPut one memory under
Put one memory under
everything you use.
Connect a tool, save one conversation, and recall it in the next one. Free during early access — about 100 saves a day.