Alternatives
Products that do what Hopsule – Persistent Memory Layer for AI Engineering does
Hey Everyone, I'm neither the founder or affiliated with these guys. But when they showed me the product it really clicked a switch. I have been building products with AI since sonnet 4.0, and one of my issue, like many, consistency. Hopsule turns architecture decisions into enforceable context that AI tools must follow. Creates trackable, tasks which can be feed into your AI tools to do compound engineering. If you're building with Claude Code, Cursor, or Copilot. You can use their CLI or MCP.
- 1HP
Hi HN! I'm building Hopsule. If you use AI coding tools like Cursor, Copilot, or Claude, you’ve probably seen this happen: The AI writes good code - but it ignores your architecture. It doesn’t know: - why you chose a specific pattern - which conventions your team agreed on - which decisions are already locked in So it falls back to generic patterns, outdated examples, or random GitHub training data. Over time this slowly breaks the consistency of the codebase. Most teams try to fix this with: - giant Markdown files - wiki pages - long prompts - Slack threads But those aren't…
Mar 2026
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16PM
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
- 17CO
Hey HN! We're Vasilije, Laszlo and Lazar, the authors of a new paper and part of https://www.cognee.ai. cognee let’s you build memory layers for AI applications and agents, allowing them to personalize results, connect various data sources, and add custom rules. This enables AI apps to deliver increasingly accurate responses, we reached almost 90% on standard industry benchmarks as you can see here https://github.com/topoteretes/cognee/tree/main/evals and our paper can be accessed at: https://arxiv.org/abs/2505.24478 and collab…
2025 · github.com
- 18SA
I built Syne because I was tired of AI assistants that forget everything after each conversation. Syne is a self-hosted AI agent framework where memory is a first-class citizen — stored as semantic vectors in PostgreSQL, searchable across millions of entries, and persistent forever. Key features: - Unlimited persistent memory with semantic search (pgvector) - Anti-hallucination: only stores user-confirmed facts, auto-deduplicates - Self-evolving: creates new abilities at runtime without restart - Multi-model: switch between Gemini, ChatGPT, Claude mid-conversation - True $0/month setup:…
Feb 2026
- 19DP
Hello HN, I'm Ali, building Decispher. The problem we're working on is that coding agents repeatedly rediscover context that already exists inside an engineering organization. A developer working on a feature can combine information from previous PRs, Jira tickets, Slack discussions, ownership boundaries, architectural decisions and their own experience. Coding agents usually start with a prompt and a repository, then spend tokens searching for that same context—or miss it entirely. Decispher is a context and memory layer for engineering agents. It currently has three parts: 1) Context…
6d ago
- 20WA
Today you can easily adopt AI coding tools because you have git for branching and rolling back if AI writes bad code. We haven't seen this same capability for data and decided to build it ourselves. Nile is a new kind of data lake, purpose built for using with AI. It can act as your data engineer or data analyst creating new tables and rolling back bad changes in seconds. We support real versions for data, schema, and ETL. We'd love your feedback on any part of what we are building - https://getnile.ai/ What do you think?
Jan 2026
- 21
- 22PM
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
- 23AM
Hey HN, I'm Namanyay and I've been using Cursor since 2 years, but it seems to make mistakes as the project size grows. This caused me to have to repeat myself a lot and it used to break my flow. I realized it's because Cursor (and other AI tools) are not able to keep an overview of the project. Plus, Cursor does not have a "memory" layer to remember important things that the user has already mentioned. I solved this by building an open-source MCP which maintains project and memory information within the user's file system. It's simple and installation takes 30 seconds. Github:…
2025
- 24MA
Hi HN, A couple weeks ago I shared an early version of a side project I’ve been tinkering with called Persistent Mind Model. I built it at home on an i7-10700K / 32GB RAM / RTX 3080 because I was curious whether an AI could keep a stable “mind” over time, that could "think" about it's own identity as an LLM, instead of resetting every session. After a lot more tinkering, I think the architecture is finally in a solid place. Basically, it saves everything the AI does, thoughts, decisions, updates as a chain of events in a local SQLite database. Because the “identity” is stored in…
Nov 2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →