letta
★ 25.2k
vs
engrim
★ 299
letta vs engrim
letta: Letta is a powerful platform for building stateful AI agents equipped with advanced memory, enabling them to learn and self-improve over time. It provides both a command-line interface for local agent execution and a comprehensive API with Python and TypeScript SDKs for seamless integration into applications.; 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
lettaMemory & Context · ★ 25.2k
When to choose:
- You want a long-lived agent that remembers past work and rewrites its own memory and context over time.
- You want one agent reachable from CLI, desktop, browser, mobile and messaging apps, with subagents, schedules and hooks.
- You want memory you can inspect: the README says context is tracked in git and can sync to your own repository.
When to skip:
- You only need to add memory to an agent you already use through MCP; a small MCP memory server is a lighter fit.
- You rely on older Letta tutorials or the V1 API server: the project restructured, and the V1 server is retired.
- You want everything to work without signing in: Letta Cloud is the default backend and some features need it.
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.
02
Side-by-Side Comparison
Field
lettaengrimCategory
Memory & Context
Memory & Context
Stars
★ 25.2k
★ 299
License
Apache-2.0
MIT
Install Command
npm install -g @letta-ai/letta-code
pip install engrim
Updated
5d ago
3w ago
Open Source
Yes
Yes
Tags
Stateful AI, Agent Platform, Advanced Memory
Episodic Memory, LLM Context Management, AI Agents
03
Features
letta01Build stateful AI agents with advanced memory
02Agents capable of learning and self-improvement over time
03CLI tool for running agents locally in your terminal
04Comprehensive API for integrating agents into applications
05Support for skills and subagents; fully model-agnostic
engrim01Precision 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
letta↳Running AI agents locally in your terminal for coding and general tasks.
↳Integrating stateful AI agents into custom applications using the API and SDKs.
↳Developing self-improving AI systems that adapt and learn continually.
engrim↳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.
05
Best For
lettaMost PopularEssentialTrending
engrim—
FAQ
FAQ
What is the difference between letta and engrim?
Both letta and engrim are in the Memory & Context category. letta has 25.2k stars, while engrim has 299 stars.
Which is better, letta or engrim?
The best choice depends on your use case. Choose letta if Running AI agents locally in your terminal for coding and general tasks., 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 letta free or open source?
Yes, letta is open source on GitHub (Apache-2.0).
Is engrim free or open source?
Yes, engrim is open source on GitHub (MIT).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→