Engram
Persistent, searchable memory for AI coding agents in a single Go binary backed by SQLite.
Sources and review
Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.
Keeping decisions and conventions available to a coding agent across sessions without running extra services.
About Engram
Engram gives coding agents a project memory that survives between sessions. It is a single Go binary using SQLite with FTS5 full-text search, exposed through an MCP server, an HTTP API, a CLI and a terminal UI, and works with MCP-compatible agents including Claude Code, OpenCode, Gemini CLI, Codex, Cursor and Windsurf. It needs no Node.js, Python or Docker; an optional cloud sync is offered separately.
Engram is listed in this index written primarily in Go, with 7.7k stars on GitHub. Its latest recorded repository push was in November 2026; that is not an ASE editorial review date.
Before connecting: access and data
This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.
- List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
- Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
- Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
- Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.
brew install gentleman-programming/tap/engram