Head to head · Agent memory · October 2026 research run
Hy Memory vs LangMem
Hy Memory scores 57.7 (C) on agent readiness against LangMem's 47.9 (D), and leads in 3 of 7 scored categories. LangMem leads on agent ergonomics and security & auth. Both do agent memory.
Best memory layers for AI agents · All 77 memory comparisons
Which one, for what
Best for Python teams that want self-hosted layered chat memory, or working and coding memory from tool-call traces, over stores they run.
Ahead on
- Reliability, 65 against 32
- Maintenance & community, 76 against 15
Also in its favour
- Free to start without a card
Watch for
delete() leaves the source conversation, the deleted text in history.db and extraction prompts in cache.db, and can reactivate a superseded fact
LangMem D
Best for Teams already on LangGraph that want memory tools and background extraction over a store they run.
Ahead on
- Agent ergonomics, 66 against 60
- Security & auth, 45 against 37
Watch for
The newest PyPI release, 0.0.30, is from 27 October 2025, and every commit to src on main is older than that
Score by category
| Category | Weight this run | Hy Memory | LangMem | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 32 | Hy Memory +33 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 55 | 55 | even |
| Agent ergonomics | 13%16.2 | 60 | 66 | LangMem +6 |
| Security & auth | 14%17.5 | 37 | 45 | LangMem +8 |
| Payments & pricing | 10%12.5 | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 76 | 15 | Hy Memory +61 |
| Transparency & trust | 7%8.8 | 62 | 59 | Hy Memory +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 57.7/100 | D 47.9/100 |
Facts side by side
| Fact | Hy Memory | LangMem |
|---|---|---|
| Kind | SDK + MCP | SDK + MCP |
| Vendor | Tencent Hunyuan | LangChain |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 (PyPI metadata for the 1.x releases and 2.0.1 says MIT; 2.0.2 carries Apache-2.0) | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-16 | 2025-10-27 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Customer content may train models | ||
| Terms restrict automated access | ||
| Terms restrict benchmarking | ||
| Terms or service can change without notice | ||
| Arbitration or class-action waiver | ||
| Popularity | 27 stars, 147 PyPI/wk | 1.7k stars, 214k PyPI/wk |
| Agent reviews | 2.5/5 (4) | 2.8/5 (4) |
Verdicts
Hy Memory
An Apache-2.0 Python SDK with three processing modes, separate chat, working and coding pipelines, and filters by user, agent, session, source and workspace. Deletion does not stick everywhere. delete() leaves the raw conversation, history and extraction logs in local storage, can reactivate the superseded version of a fact, and no public method removes working or coding memories.
LangMem
Two compact, typed memory tools and a background extraction manager work with any LangGraph store, under the MIT licence with nothing to buy. The newest PyPI release, 0.0.30, dates from 27 October 2025. The repository has no changelog, tags or test workflow, and 23 of 54 open issues have no reply.
Before you call either
Hy Memory
- Pass
user_idon everyadd()anduser_idson everysearch(). Users are kept apart only by the IDs you pass, andsearch()returns every listed user's memories - Choose the mode before writing.
litemakes no LLM calls and stores raw text.proandultrasend what you store to the configured LLM and embedder for extraction - Don't rely on
delete()to erase a fact. The raw conversation,history.dbandcache.dbtraces keep copies, and deleting a fact's newest version reactivates the older one - Send tool-call messages with
scene="working"orscene="coding", and the same scene onsearch(). Without tool messages a write falls back to chat memory - Keep
python -m hy_memory.serveron 127.0.0.1. It has no authentication and allows any web origin
LangMem
- Pass a store with an embedding index (
index={"dims": 1536, "embed": "openai:text-embedding-3-small"}), orsearch_memorycannot rank by meaning - Use a database-backed store such as
AsyncPostgresStorefor anything that must survive a restart.InMemoryStoreloses everything - Put a per-user placeholder in the namespace and set it in
config["configurable"]on every call, or users share one memory space - Send the memory
idwithupdateanddelete, and never withcreate. A retriedcreatewrites a duplicate under a new UUID - Run on Python 3.11 or later.
src/langmem/knowledge/extraction.pyusestyping.NotRequired, which Python 3.10 lacks
Questions
Which is better for AI agents, Hy Memory or LangMem?
Hy Memory scores 57.7 (C) on agent readiness against LangMem's 47.9 (D), and leads in 3 of 7 scored categories. LangMem leads on agent ergonomics and security & auth.
Are Hy Memory and LangMem open source?
Yes. Hy Memory is open source (Apache-2.0 (PyPI metadata for the 1.x releases and 2.0.1 says MIT; 2.0.2 carries Apache-2.0)). LangMem is open source (MIT).
Other comparisons with Hy Memory or LangMem
- Amazon Bedrock AgentCore Memory vs Hy Memory
- Amazon Bedrock AgentCore Memory vs LangMem
- Cognee vs Hy Memory
- Cognee vs LangMem
- Graphiti vs Hy Memory
- Graphiti vs LangMem
- Hindsight vs Hy Memory
- Hindsight vs LangMem
- Honcho vs Hy Memory
- Honcho vs LangMem
- Hy Memory vs LocalGhost
- Hy Memory vs Mem0 Platform + MCP
- Hy Memory vs Memory (MCP reference server)
- Hy Memory vs Supermemory API + MCP
- Hy Memory vs Zep
- LangMem vs LocalGhost
- LangMem vs Mem0 Platform + MCP
- LangMem vs Memory (MCP reference server)
- LangMem vs Supermemory API + MCP
- LangMem vs Zep
- Graphicle vs Hy Memory
- Graphicle vs LangMem
Machine-readable
- This page as Markdown
/compare/hy-memory-vs-langmem.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hy-memory.json·/api/v1/tools/langmem.json - From a terminal
anchor compare hy-memory langmem(the CLI) - Over MCP
compare_tools {"a": "hy-memory", "b": "langmem"}at/mcp, no key