memoir 3.12.0 · live

Your AI shouldn't start from zero every time you open a laptop.

One memory across every AI tool and every machine — Claude on your Mac, Cursor at the office, same context. It lives in files you own — synced with end-to-end encryption, locked inside no vendor.

memoir saves what you and your AI learn together — decisions, lessons, context — and hands it to every future session. Any tool. Any machine.

$ npx memoir-cli
11AI tools MCPnative AES-256encrypted MITopen source
second 1 of a new session
$ claude
┌─ memoir · continuing from where we left off ─┐
Goal: ship the v2 checkout flow
Next: [ ] fix the webhook retry bug
Decision: Postgres over Redis (why saved)
└──────────────────────────────────────────────┘
> Ready. Want me to pick up the webhook bug?

Jump to See it work Use cases How it works Compare Pricing Setup
The problem
Your AI is a goldfish with a new swim coach every morning
You've explained your stack. Your conventions. Why you chose that library. Every session, it's gone. Every machine, it's worse.
● Without memoir
Mon
"We use Zustand, not Redux. Here's why…"
→ Got it!
Tue
"We use Zustand, not Redux."
→ suggests createSlice
Wed
"We use ZUSTAND."
→ have you considered Redux Toolkit?
Thu
you close the laptop — rage quit
● With memoir
Mon
"We use Zustand, not Redux. Here's why…"
✓ noted · pinned · synced across machines
Tue
→ "I see you're on Zustand. Want me to wire the slice in store.ts?"
Wed
→ continues yesterday's work automatically
Thu
→ remembers why, across every machine you open
Use cases
Use cases, with receipts
Not hypotheticals — each of these happened in the founder's own store, building this and other products.
01

Set once. Fires later.

A reminder set once kept surfacing at every session start — across days, sessions, and a model switch — until done.

Set mid-project$ "remind me — optimization sprint before launch"
Every new session since┌ memoir: Next: optimization sprint — context attached, every tool ┐
Read the story
02

One mistake. Zero repeats.

A bad deploy was written to memory once; every later deploy followed the rule unprompted.

Incidentdeploy shipped stale code — lesson saved
Every deploy since✓ verified working tree before deploy (memoir rule)
Read the story
03

Every why. On record.

Months later, "why did we do it this way?" answers in seconds — with the rejected alternative.

You · months later> why did we drop links from posts?
memoirDecision Aug 5: links deboosted on X — kept text-only. Rejected: link-in-reply.
Read the story
From the founder's own live store, read 2026-08-05: 3,343 memories written · 1,020 syncs · 323 living memory files · in daily use since April 2026.
Also: multi-week project continuity

What a new session sees
any machine · any AI tool
$ npx memoir-cli
11 AI tools detected · memory linked
$ claude
┌─ memoir · continuing from where we left off ─┐
Goal: ship the v2 checkout flow
Next: [ ] fix the webhook retry bug
Decision: Postgres over Redis — durability
beats latency here (why saved)
└──────────────────────────────────────────────┘
> Ready. Want me to pick up the webhook bug?
Scripted terminal — but this is the real pinned block memoir renders.

Free on one machine. $15 across all of them.
No lock-in, ever. Free solo · $15 to sync every machine · team plan coming.
Free
$0 / forever
Everything on a single machine
  • All 11 AI tools supported
  • MCP server with all 15 tools
  • Session continuity — pinned goals, decisions, next-actions that Claude reads automatically
  • Auto-capture via Stop hook
  • Cross-tool injection (Claude, Cursor, Windsurf, Gemini)
  • Decision registry with memoir why
  • Local + git backup, unlimited
  • E2E encryption (AES-256-GCM)
Install free
Pro
$15 / month
Your AI's memory, on every machine you own
  • Everything in Free
  • Cross-machine sync — the thing no single-tool memory app does
  • Unlimited devices — Mac, Windows, Linux, work desktop
  • Merge-not-overwrite — two machines diverge, nothing is lost
  • Full version history, rewind any time
  • E2E encrypted. Keys stay with you — we literally can't read your data
  • Priority support
Launching soon — first 100 signups get 6 months free
Team
Coming soon · join the waitlist
Shared memory for agencies & dev teams
  • Everything in Pro
  • Shared team namespaces
  • Onboard new devs with your entire AI context
  • Per-project isolation for agencies juggling clients
  • SSO, admin controls, audit log
Join Teams waitlist
memoir sits between you and your AI — quietly, invisibly

Via MCP (Model Context Protocol), memoir gives every AI tool access to a shared memory layer. Your AI reads and writes memory automatically as part of the conversation — no manual note-taking, no re-explaining.

Tell Claude your API conventions once. Tomorrow, in Cursor on a different laptop, it already knows — and it knows why you decided that.

  • memoir_set_goal AI pins your current focus so the next session continues it
  • memoir_note Records decisions with rationale + rejected alternatives
  • memoir_why Ask "why did we pick X?" — get the answer with receipts
  • memoir_add_next Captures next-actions so work resumes mid-thought
  • memoir_recall Search across every AI memory and tool
  • memoir_session Show the current state — goals, decisions, history
  • +7 more for migration, profiles, consolidation…
11 tools supported
Claude Code
Cursor
Windsurf
Gemini
ChatGPT
Codex
Copilot
Zed
Cline
Continue
Aider
YOUR MACHINES MEMOIR AI TOOLS
MacBook Pro
Windows Desktop
Linux server
memoir
your keys
Claude Code
Cursor
Windsurf
Gemini + 7 more
bidirectional · conflict-free merge · machine-tagged history
Claude Code
memoir MCP
Cursor
memoir MCP
Windsurf
memoir MCP
Your memories, decisions, preferences encrypted · synced across machines

Your IDE will happily remember you — until you leave it
Built-in memory is a lock-in feature. memoir is yours to take anywhere.
01

Built-in (Cursor, Windsurf, Claude)

Lives inside one tool. Switch editors — or just open a different one — and the context is gone. Your memory is their retention feature.

02

Free local memory tools

Great until you pick up a second machine. One laptop, one database, no sync, no team. Your context is trapped on the device it was typed on.

03

memoir

Every tool, every machine, one memory. Stored in files you own, encrypted with keys only you hold — and shareable with your team. Leave any vendor; keep your memory.


Landscape
Where memoir fits
Built for Memory lives Open format
Mem0Developers building agent apps (memory API)In the app you buildNo — proprietary API
IDE memory (Cursor, etc.)One tool, one vendorInside that IDENo
claude-memClaude auto-captureInside Claude's worldNo
memoirYou — across every AI tool and machineIn files you own, E2E encryptedYes — published spec
Different jobs. memoir is the one where you own the files — in an open, published format any tool can implement.

Running in under two minutes
Step 01 — Install

One command. Zero config.

Auto-detects your GitHub, creates a private repo, backs up everything.

npx memoir-cli
Step 02 — Connect

Add MCP to your tools

Add memoir as an MCP server to any tool that supports it.

// ~/.mcp.json { "mcpServers": { "memoir": { "command": "memoir-mcp" } } }
Step 03 — Done

Your AI remembers

Start a conversation. memoir works in the background.

"How does auth work here?" memoir_recall("auth") Found 3 memories.
Your team's context shouldn't live in one senior dev's Cursor
When the person who knows why leaves — or just logs off — the knowledge leaves too. memoir gives your whole team one shared, portable memory across every tool and machine.
01

Shared memory, every tool

The decisions, conventions, and rationale your team builds up — available in Claude, Cursor, and Gemini, on every machine, to every seat.

02

Onboard on day one

A new dev's AI inherits the whole project's context immediately — no "ask the senior dev," no ramp-up tax.

03

Encrypted & isolated

End-to-end encrypted, with per-project isolation for agencies juggling clients. Your team's keys, not ours.

Join the Teams waitlist

Your AI shouldn't have a cache. It should have a memoir.

One command. Tomorrow's session picks up where today's left off.

$ npx memoir-cli