The problem
Your agent forgets everything
when the session ends.
Every time you start a new session, your AI coding agent has zero context. The bug you fixed yesterday, the architecture decision you made last week, the conventions your team follows — gone. You repeat yourself, re-explain context, and watch the same mistakes happen again.
Engram gives your agent a persistent, searchable memory layer. You never start from zero again.
Features
Everything you need,
nothing you don't.
Designed for developers who value their time and tools. No Node.js, no Python, no Docker. One binary.
Agent agnostic
Works with any MCP-compatible agent. Claude Code, OpenCode, Gemini CLI, Codex, VS Code, Cursor, Windsurf, or anything else you throw at it.
SQLite + FTS5 search
Full-text search built-in. Zero external processes.
Your memories are a single engram.db file.
One binary, zero deps
A single Go binary. No Node.js, no Python, no Docker, no Chrome DB.
go install and you're done.
Interactive TUI
engram tui launches a beautiful terminal UI.
Navigate, search, and explore memories with vim keys.
15 MCP tools
mem_save, mem_search, mem_context, mem_session_summary, mem_timeline, and 10 more. Standard MCP protocol — plug in and go.
Git sync
Share memories across machines with engram sync.
Uses compressed chunks — no merge conflicts, no huge files.
How it works
Three steps to a
permanent memory.
Install once
One brew install command. Or download the binary directly for
Windows and Mac/Linux. No runtime, no dependencies, no setup scripts.
brew install gentleman-programming/tap/engram Agent save memory
You do nothing. Agents call mem_save for bugfixes,
decisions, discoveries, and conventions automatically.
Key moments stay ready for later.
mem_save("Fixed N+1 query in UserList") Next session: context loaded
Start a new session and your agent automatically searches past memories, resumes where you left off, and never asks you to re-explain the codebase.
mem_context() → 24 memories loaded Compatibility
Works with every agent
you already use.
Standard MCP protocol. If it speaks MCP, it works with Engram.
Claude Code
Plugin marketplace
engram setup claude-code OpenCode
Built-in setup
engram setup opencode Gemini CLI
Built-in setup
engram setup gemini-cli Codex
Built-in setup
engram setup codex VS Code
Built-in setup
engram setup vscode-copilot Cursor
Built-in setup
engram setup cursor Windsurf
Built-in setup
engram setup windsurf Pi
Built-in setup
engram setup pi Kiro
Built-in setup
engram setup kiro Kilo Code
Built-in setup
engram setup kilocode Qwen Code
Built-in setup
engram setup qwen Antigravity CLI
Built-in setup
engram setup antigravity-cli Any MCP Agent
Standard protocol
engram mcp Comparison
Better by design.
Not by accident.
Engram is inspired by claude-mem. But made different.
| Feature | Engram | claude-mem |
|---|---|---|
| Language | Go (single binary) | TypeScript + Python |
| Agent lock-in | None — any MCP agent | Claude Code only |
| Search | SQLite FTS5 (built-in) | ChromaDB (extra process) |
| Storage | Single .db file | SQLite + ChromaDB |
| Dependencies | Zero | Node.js, Bun, uv, Python |
| Processes | One binary | Worker + ChromaDB |
| Auto-capture | Agent decides (clean) | All calls then compress |
| License | MIT | AGPL-3.0 |
Open Source
Built in public.
Open for everyone.
Engram is MIT licensed and actively maintained. Every decision is made in the open — audit the code, open an issue, or submit a PR.
How to contribute
- Fork the repository
- Create a feature branch
- Open a Pull Request
Get started
Your agent's
memory starts
today.
One command. Persistent memory. Works with every agent you already use. No Node.js, no Python, no Docker. Just a single binary.