v0.3.1 — Claude Code + Cursor + Codex CLI

Your AI tools
finally have a memory.

Every AI coding session starts blank. Decisions, dead ends, architecture choices — gone. mnemo watches your sessions, extracts what matters, and injects it back. Automatically.

zero-config TypeScript-native dev-tool-specific auto-capture
npx mnemo-ai init view on github →
0
Zero-config
One command and you're done. No YAML, no dashboard, no setup wizard. npx mnemo-ai init — that's it.
TS
TypeScript-native
Built in TypeScript, for TypeScript developers. First-class MCP support. Runs anywhere Node runs.
</>
Dev-tool-specific
Purpose-built for AI coding workflows. Not a generic note-taking app. Understands decisions, patterns, and code references.
↻
Auto-capture
Memories are extracted automatically from your sessions. You don't write anything manually. Just code — mnemo remembers.
⌕
Status awareness
Shell prompt shows [mnemo] when active. Your AI tools see a live status line — memory count, branch, last capture.
⊕
100% local
All memories stored in SQLite on your machine. Nothing leaves your disk. Your code context stays yours.
works with
Built for the tools you use.
Claude Code SUPPORTED
Cursor SUPPORTED
Windsurf COMING SOON
Codex CLI SUPPORTED
Aider COMING SOON
Continue COMING SOON
Cline / Roo COMING SOON
~/projects/api-service
$ mnemo recall "how did we handle auth?"
searching: "how did we handle auth?"...
synthesizing from 4 memories...
mnemo recall — "how did we handle auth?"
Auth lives in /lib/auth.ts [4]. You chose JWT over sessions [1]
because the API needs to be stateless for horizontal scaling.
Refresh tokens are stored in Redis — you tried httpOnly cookies
first [2] but abandoned it due to CORS issues with the mobile
client. Access tokens expire in 15 min [3].
4 memories · project: api-service · branch: main
$
what mnemo captures
Five memory types.
Zero noise.
decision
Architecture and implementation choices — what you picked and why.
rejection
Approaches tried and abandoned. Prevents repeating past mistakes.
pattern
Recurring conventions specific to your codebase.
reference
Where things live. Stops the AI from searching wrong places.
error
Error patterns and their root cause fixes.
how it works
Four steps. Fully automatic.
01
mnemo init
Sets up the MCP server in your AI tool config. One command, done.
02
mnemo watch
Background daemon watches your sessions. Captures on pauses (30s) and every 5 minutes during long sessions.
03
auto-extract
mnemo reads the transcript and extracts decisions, patterns, and references into SQLite.
04
inject on start
Next session, MCP injects the right memories. Your AI arrives already knowing your project.
$ npm install -g mnemo-ai
requires Node 20+ · ANTHROPIC_API_KEY
read the docs →
pricing
Start free. Scale when ready.
Solo
Free
forever, no card required
  • unlimited local memory
  • MCP — works with any AI tool
  • all CLI commands
  • FTS5 + semantic search
  • git branch-aware scoping
Coming soon
Pro
—
cloud sync, team memory
  • everything in Solo
  • cloud sync across machines
  • team memory vault (per repo)
  • memory REST API
  • priority extraction model
  • memory analytics dashboard
Coming soon
Team
—
shared vault, admin controls
  • everything in Pro
  • shared project memory vault
  • admin: who wrote what
  • GitHub / GitLab org integration
  • Slack alerts on new captures
  • priority support