byterover-cli vs engram
Persistent project memory for AI coding agents compared
byterover-cli and engram both help AI coding agents retain and retrieve project knowledge across sessions. byterover-cli emphasizes curated context trees and integrations across coding tools, while engram centers on local SQLite memory with several access interfaces.
byterover-cli: Give Coding Agents Persistent Project Memory
ByteRover CLI is a TypeScript tool that helps AI coding agents store, search, and version structured knowledge about a project. It suits teams that want reusable context across sessions and tools, but the GitHub repository is archived and read-only.
engram: Give AI Coding Agents Persistent Memory
Engram is a Go-based memory system that helps AI coding agents retain useful project knowledge between sessions. It stores memories locally in SQLite and makes them available through MCP, a CLI, an HTTP API, and a terminal UI.
| byterover-cli | engram | |
|---|---|---|
| Language | TypeScript | Go |
| License | — | MIT |
| Stars | 5k | 7k |
| Forks | 455 | 724 |
| Last analyzed | Oct 11, 2026 | Oct 3, 2026 |
Key differences
- byterover-cli is written in TypeScript; engram is written in Go and stores memories in SQLite with FTS5 search.
- byterover-cli organizes knowledge in a context tree with branch, commit, merge, push, and pull workflows; engram provides tools to save, search, update, review, and hand off memories.
- byterover-cli lists integrations with 20 LLM providers and more than 22 AI coding agents; engram connects to MCP-compatible agents and also offers a CLI, HTTP API, and terminal UI.
- byterover-cli offers optional cloud sync and team sharing alongside local workflows; engram uses local SQLite by default, with Git Sync and optional Cloud replication.
- byterover-cli is marked archived and has a supplied license value of NOASSERTION, while its README identifies Elastic License 2.0; engram is not archived and is licensed under MIT.
Choose byterover-cli if you…
- want context organized with version-control-style branch and merge workflows.
- need integrations across multiple LLM providers and AI coding tools, plus a review workflow for proposed curation changes.
- want local context management with optional cloud sharing and a web dashboard.
Choose engram if you…
- prefer a Go-based, SQLite-backed memory store with full-text search.
- need access through MCP, a CLI, an HTTP API, or an interactive terminal UI.
- want an MIT-licensed, non-archived project with optional Git Sync or Cloud replication.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.