agent-memory vs byterover-cli
Persistent project memory for coding agents compared
agent-memory and byterover-cli help coding agents reuse project knowledge across sessions. agent-memory focuses on tiered file-based memory and generated AGENTS.md context, while byterover-cli offers a broader set of curation, version-control-style, integration, and optional cloud workflows.
agent-memory: Give Coding Agents Persistent, Tiered Memory
agent-memory turns coding-session notes into organized, tiered knowledge and generates an AGENTS.md section with relevant context for new threads. It is a TypeScript tool for teams and developers who want agents to reuse knowledge without relying on manual searches.
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.
| agent-memory | byterover-cli | |
|---|---|---|
| Language | TypeScript | TypeScript |
| Stars | 7 | 5k |
| Forks | 0 | 455 |
| Last analyzed | Oct 4, 2026 | Oct 11, 2026 |
Key differences
- agent-memory consolidates session journal notes into hot, warm, and cold memory tiers; byterover-cli organizes knowledge in a context tree with branch, commit, merge, push, and pull workflows.
- agent-memory generates an AGENTS.md section with hot memory inlined and warm memory listed; byterover-cli centers on interactive querying and curation, with a review workflow for proposed changes.
- agent-memory stores memory in files and documents Amp and generic shell adapters; byterover-cli supports local workflows plus optional cloud sync, team sharing, and a web dashboard.
- byterover-cli lists integrations with 20 LLM providers and more than 22 coding agents, as well as MCP; agent-memory describes adapter-based integration and a CLI.
- Both are TypeScript projects, but agent-memory documents a standalone workflow using Bun, while byterover-cli's npm installation requires Node.js 20 or newer.
- The supplied facts list agent-memory as not archived with 7 stars and 0 forks, and byterover-cli as archived with 5k stars and 454 forks; byterover-cli also has a supplied license value of NOASSERTION, while its README identifies Elastic License 2.0.
Choose agent-memory if you…
- want tiered memory generated from session notes, with relevant context added to AGENTS.md.
- prefer file-based storage and a standalone CLI with adapter-based integrations.
- need to reorganize accumulated notes through consolidation and defragmentation.
Choose byterover-cli if you…
- want context organized with version-control-style branch, commit, merge, push, and pull workflows.
- need interactive knowledge curation, querying, and review of proposed changes.
- want optional cloud sharing or integrations across multiple coding tools, and have checked the project's archived status and license terms.
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.