krimto-labs/krimto

> Open-source memory for AI coding agents you own in git — governed by a real user→team→org hierarchy, not a vendor database. Solo to team. Apache-2.0.
Your agent's memory, as markdown in your own git — synced across every editor and machine. Tell your
agent "remember X" in any editor and it saves a durable, attributable fact; ask later — in a new chat,
a different editor, or on another machine — and it recalls the right answer. One command, no account,
no vendor database: your memory follows you.
You own it: every fact is a plain markdown file in a git repo you control — readable, reviewable in a
PR, and yours. When a teammate joins, that same memory becomes a shared team brain governed by a real
user → team → org hierarchy (the most specific scope wins at recall) — the one primitive no other
memory tool ships. Solo is free; the governance is what you grow into.
See it
One npx command sets it up; then your agent saves a fact in Claude Code and recalls it in Cursor —
no account, no database:
Three short demos — **solo** (remember in Claude Code, recall in Cursor), **cross-machine** (write,
git push, recall on another laptop), and **team** (a teammate's fact reaches you; your personal notes
stay yours).
Because every memory is just a file in your git, you can read it yourself — no API, no dashboard needed:
That's the whole bet: **your agent's memory is plain markdown in a git repo you own — not rows in
someone else's database.**
Why Krimto
- **You own it, in your git.** Every fact is a markdown file in a git repo you control — git log the
audit trail, edit it in any editor, review it in a pull request. No vendor database, no lock-in.
- **Governed user → team → org hierarchy.** Knowledge is scoped to a person, a team, or the whole
company, and the most specific scope wins at recall — a server-enforced primitive no other memory
tool ships for free.
- **Follows you everywhere — cross-vendor, Apache-2.0.** One MCP server syncs the same memory across
Claude Code, Cursor, Codex, Gemini CLI and more — every editor and machine. Fully open source, with
no managed-service restriction.
Try it in 2 minutes (solo, no account)
The setup wizard detects your editor, wires it up, and turns on automatic memory. Then, in any chat:
Open a new chat and ask:
See your notes with krimto notes (terminal) or krimto ui (browser dashboard). Your data lives in
~/.krimto — the same folder no matter which project you're working in.
Connect your agent
krimto init wires supported editors for you. What auto-connects vs. needs one copy-paste step:
| Editor | Setup |
|---|---|
| Cursor | auto-connects |
| Claude Code | auto-connects |
| Codex | manual snippet |
| Gemini CLI | manual snippet |
To connect any MCP client manually, point it at Krimto over stdio:
…or the config-file form (Cursor, Codex, Gemini CLI, etc. use the same shape):
By default an agent uses Krimto only when you ask. Running krimto init once in your project drops a
standing rule so it uses Krimto on its own.