ai-memory vs byterover-cli
Persistent project memory for coding agents compared
ai-memory and byterover-cli help coding agents reuse project knowledge across sessions and tools. ai-memory captures activity into a self-hosted, git-backed Markdown wiki, while byterover-cli centers on curated structured memory, with local workflows and optional cloud sync.
ai-memory: Share Long-Term Memory Across Coding Agents
A self-hosted Rust service that captures coding-agent activity into a searchable, git-backed Markdown wiki and hands work between agents. It suits developers and teams who want portable project memory without requiring LLM calls.
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.
| ai-memory | byterover-cli | |
|---|---|---|
| Language | Rust | TypeScript |
| License | MIT | — |
| Stars | 9.1k | 5k |
| Forks | 632 | 455 |
| Last analyzed | Oct 10, 2026 | Oct 11, 2026 |
Key differences
- ai-memory captures prompts, tool calls, and session boundaries through agent integrations; byterover-cli focuses on developers curating and querying knowledge through an interactive REPL and review workflow.
- ai-memory stores its source of truth as ordinary Markdown files; byterover-cli organizes knowledge in a context tree with branch, commit, merge, push, and pull workflows.
- ai-memory is a Rust server and CLI designed for self-hosting; byterover-cli is a TypeScript CLI with local workflows and optional hosted cloud sync and team sharing.
- ai-memory supports search and handoffs without requiring LLM API calls; byterover-cli integrates with LLM providers and includes tools for code execution, file operations, search, and memory management.
- ai-memory uses an MIT license and is not archived; byterover-cli is marked archived, and its supplied license data is NOASSERTION, while its README identifies Elastic License 2.0.
- ai-memory has 8.8k stars and 608 forks; byterover-cli has 5k stars and 454 forks.
Choose ai-memory if you…
- want project knowledge stored as inspectable, editable, git-backed Markdown files.
- need capture and handoffs that work without LLM API calls.
- prefer a self-hosted server for sharing memory across machines and teammates.
Choose byterover-cli if you…
- want to curate structured knowledge with a context tree and version-control-style workflows.
- need integrations with multiple LLM providers and coding agents, plus MCP support.
- want optional cloud sync, team sharing, or a review process for proposed knowledge changes.
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.