AgentIndex icon
AgentIndex
remem logo
remem
★ 34
vs
engrim logo
engrim
★ 299

remem vs engrim

remem: `remem` is a local-first memory solution for AI coding agents like Claude Code and OpenAI Codex, preventing repetitive explanations by automatically capturing and injecting project context. It distills, searches, and stores project decisions, bug fixes, and preferences locally using SQLite, accessible via CLI, hooks, and a REST API.; engrim: Engrim is a universal, local-first SQLite memory engine specifically engineered for autonomous AI coding agents, designed to solve the '200,000-token context window trap'. It provides high-precision, curated episodic working memory, allowing developers to switch between various models and environments on the same codebase without losing architectural decisions or project state.

01

TL;DR

remem logo
rememMemory & Context · ★ 34

Avoiding repetitive project explanations to AI coding agents.

Read remem full review →
engrim logo
engrimMemory & Context · ★ 299

Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched.

Read engrim full review →
02

Side-by-Side Comparison

Field
remem logoremem
engrim logoengrim
Category
Memory & Context
Memory & Context
Stars
★ 34
★ 299
License
MIT
MIT
Install Command
curl -fsSL https://raw.githubusercontent.com/majiayu000/remem/main/install.sh | env REMEM_NO_CONFIG=1 sh && ~/.local/bin/remem install --target codex
pip install engrim
Updated
2d ago
3w ago
Open Source
Yes
Yes
Website
↗ Visit
↗ Visit
GitHub
↗ GitHub
↗ GitHub
Tags
AI Agent Memory, Context Management, Coding Assistant
Episodic Memory, LLM Context Management, AI Agents
03

Features

remem logoremem
01Automatic memory capture and injection for coding agents.
02Searchable history of project decisions, bug fixes, and rationale.
03Local-first memory storage with SQLite and SQLCipher encryption.
04Accessible via CLI, coding agent hooks, MCP tools, and REST API.
05Single Rust binary with no external database dependencies.
engrim logoengrim
01Precision Working Memory: Replaces raw transcript replay with ~4,000 characters of high-precision, curated episodic memory, injected at boot with zero attention dilution.
02Cross-Model/Agent Compatibility: Provides a universal substrate for memory, allowing decisions made in one agent (e.g., Claude Code) to be visible and usable in others (e.g., Antigravity, Cursor).
03Local-First & Private Storage: Stores all memories locally in a SQLite file (~/.engrim/memory.db) with WAL mode and POSIX 0600 permissions, ensuring 100% privacy with no cloud sync or telemetry.
04Self-Healing Diagnostics: The `engrim doctor --fix` command verifies all hooks and installs portable PATH fallbacks, ensuring reliable operation across machines and OSes without silent failures.
05Hybrid Retrieval & Minder: Employs a hybrid lexical (BM25) and vector (model2vec) search for efficient and relevant memory recall in approximately 30ms.
04

Use Cases

remem logoremem
↳Avoiding repetitive project explanations to AI coding agents.
↳Searching and recalling past project decisions and bug-fix rationale.
↳Maintaining an auditable and project-scoped history of engineering memory.
↳Reducing the need for manual upkeep of large memory documentation files.
engrim logoengrim
↳Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched.
↳Collaborative Multi-Agent Development: Enabling multiple AI coding agents (e.g., Antigravity, Claude Code, Cursor) to work on the same codebase and share a consistent, evolving memory store.
↳Continue-As-Clear Workflow: Allows users to clear their agent's context window at any time, with Engrim automatically re-injecting the active memory pack for seamless continuation without memory loss.
↳Auditing Agent Provenance: Tracking which agent made specific architectural decisions or added facts to the project's memory, enhancing transparency in multi-agent environments.
FAQ

FAQ

What is the difference between remem and engrim?
Both remem and engrim are in the Memory & Context category. remem has 34 stars, while engrim has 299 stars.
Which is better, remem or engrim?
The best choice depends on your use case. Choose remem if Avoiding repetitive project explanations to AI coding agents., and engrim if Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched..
Is remem free or open source?
Yes, remem is open source on GitHub (MIT).
Is engrim free or open source?
Yes, engrim is open source on GitHub (MIT).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related

Alternatives to remem →Alternatives to engrim →remem details →engrim details →