Alternatives
Products that do what Claude-engram – Brain-inspired persistent memory, runs inside Claude.ai does
Claude.ai artifacts can call the Anthropic API and have persistent storage (5MB via window.storage). I used these two capabilities to build a memory system modeled on how human memory actually works — salience scoring, forgetting curves, and sleep consolidation — all running inside a single React artifact with no external dependencies. Just add artifact to your chat and paste instructions into your personal preferences setting.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9AM
Hi HN, I have been recently geeking on agentic memories, and I believe I finally came up with something that works. I spent the last couple of weeks building a memory[0] for Claude Code that dynamically evolve as you talk with it. I followed a new paradigm inspired from zettelkasten method. Whenever Claude discover something new in the codebase or during your conversation with it, it writes a note about it, link it with related memories, update the related memories accordingly, and store it in chromaDB (this part where it keeps self-evolving based on new inputs). Later when you ask it to…
Jan 2026 · github.com
- 10
- 11
- 12PM
This is my attempt in building a memory that evolves and persist for claude code. My approach is inspired from Zettelkasten method, memories are atomic, connected and dynamic. Existing memories can evolve based on newer memories. In the background it uses LLM to handle linking and evolution. I have only used it with claude code so far, it works well with me but still early stage, so rough edges likely. I'm planning to extend it to other coding agents as I use several different agents during development. Looking for feedbacks!
Jan 2026 · github.com
- 13
- 14
- 15
- 16
- 17
- 18
- 19PM
I built an MCP server that gives Claude Code long-term memory across sessions, backed by infrastructure you control. Every Claude Code session starts from zero, no memory of previous sessions. This server uses mem0ai as a library and exposes 11 MCP tools for storing, searching, and managing memories. Qdrant handles vector storage, Ollama runs embeddings locally (bge-m3), and Neo4j optionally builds a knowledge graph. Some engineering details HN might find interesting: - Zero-config auth: auto-reads Claude Code's OAT token from ~/.claude/.credentials.json, detects token type (OAT vs…
Feb 2026 · github.com
- 20
- 21
- 22IB
I wanted to share a project I have been working on over the past week. It is a simple local memory system that saves your sessions into Markdown files, which can be viewed later. I developed this after using Claude Mem. I really enjoyed working with it, but it was consuming a lot of RAM, and each Claude session was becoming a major resource hog. I also tried other plugins and MCP solutions, but ran into similar issues, either slow performance or concerns about data being sent elsewhere. Because privacy was a big thing for me, I decided to build my own solution that keeps all data local.
Feb 2026 · github.com
- 23
- 24AA
Hi HN. Live-Memory is an open-source Claude Code plugin / MCP server that serves as an always up-to-date memory of your codebase. It uses a separate, low-cost, large-context-window model to distill your repo's organization, conventions and general structure. It observes the primary agent's activity and builds an understanding of your repo passively over time. This way, when you start a new Claude Code session, your primary agent queries Live-Memory via one read-only ask_live_memory tool and bootstraps its understanding of the codebase for the particular task at hand, instead of…
Jul 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →