amem

amem

One memory. Every AI tool.

Tell your AI something once — it remembers across Claude Code, GitHub Copilot, Cursor, Windsurf, and any MCP client.
Local-first · Semantic search · Knowledge graph · Self-evolving · Privacy-aware · No cloud required.

Quick Start • How It Works • Benchmarks • Tools • Usage Guide • Architecture

Why amem?

Every AI tool starts from zero. Every session. Every tool.

"Don't use any in TypeScript" — told Claude three times. Copilot still doesn't know.

"We chose PostgreSQL over MongoDB" — explained in Cursor. Claude has no idea.

amem gives all your AI tools a shared, persistent memory.

You (in Claude Code):  "Don't use any type in TypeScript"
  amem stores this as a correction (priority 1.0)

You (switch to Copilot): starts coding
  Copilot already knows — amem feeds it the same correction

No cloud. No API keys. Everything stays on your machine.

Quick Start

/plugin marketplace add amanasmuei/amem
/plugin install amem

copilot plugin marketplace add amanasmuei/amem
copilot plugin install amem

npm install -g @aman_asmuei/amem
amem-cli init      # Detects & configures all installed AI tools
amem-cli rules     # Generates extraction rules for proactive memory use

{
  "mcpServers": {
    "amem": {
      "command": "npx",
      "args": ["-y", "@aman_asmuei/amem"]
    }
  }
}

Verify it works:

amem-cli stats     # Should show "0 memories" initially

Tell your AI: "Remember: always use strict TypeScript, never use any type"

Start a new session: "What do you remember about TypeScript?" — it recalls instantly.

How It Works

amem captures knowledge in three layers — from fully automatic to fully manual:

Memory Types

Corrections always surface first — they are your AI's hard constraints.

Memory Tiers

Temporal Validity