AI · alternatives · 2026
24 alternatives to Decispher Memory
Memory for coding agents that learns how your team works
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Agentmemory▲310Persistent memory for Claude Code, Codex & coding agents
May 2026 · agent-memory.dev · its alternatives →
- 2DP
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…
Aug 2026 · its alternatives →
- 3
- 4
- 5
- 6RG
Hey HN! I'm José, and I built Recall to solve a problem that was driving me crazy. The Problem: I use Claude for coding daily, but every conversation starts from scratch. I'd explain my architecture, coding standards, past decisions... then hit the context limit and lose everything. Next session? Start over. The Solution: Recall is an MCP (Model Context Protocol) server that gives Claude persistent memory using Redis + semantic search. Think of it as long-term memory that survives context limits and session restarts. How it works: - Claude stores important context as "memories" during…
2025 · npmjs.com · its alternatives →
- 7
Claude-Mem▲115AI agent memory, everywhere. claude-mem is open-source memory for Claude Code; cmem links it to any MCP client — Cursor, Codex, more — via one private link.
Dec 2025 · cmem.ai · its alternatives →
- 8
Comprehensive memory management for Claude Code
Mar 2026 · codeyam.com · its alternatives →
- 9
Stop wasting tokens and re-explaining your project every session. Recall gives Claude Code durable memory — entirely offline. - raiyanyahya/recall
Jun 2026 · github.com · its alternatives →
- 10
- 11
I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…
Dec 2025 · github.com · its alternatives →
- 12
GPS▲83Memory layer for LLMs that stores repo rules + past lessons
May 2026 · github.com · its alternatives →
- 13
- 14
- 15
Persistent, shared memory for your AI coding agents
Jun 2026 · palacememory.com · its alternatives →
- 16
Tired of AI coding tools that forget everything between sessions? Every time I open a new chat with Claude or fire up Copilot, I'm back to square one explaining my codebase structure. So I built something to fix this. It's called In Memoria. Its an MCP server that gives AI tools persistent memory. Instead of starting fresh every conversation, the AI remembers your coding patterns, architectural decisions, and all the context you've built up. The setup is dead simple: `npx in-memoria server` then connect your AI tool. No accounts, no data leaves your machine. Under the hood it's TypeScript +…
2025 · github.com · its alternatives →
- 17
Open-source MCP server. #5 on LoCoMo. 100% local. MIT.
May 2026 · totalmemory.dev · its alternatives →
- 18
⚡ The open-source persistent cognitive memory layer for AI coding agents. Stop your Cursor, Claude & Copilot from having amnesia. - itskie/friday
Sep 2026 · github.com · its alternatives →
- 19
Hi HN, I'm Tony. I built Grov (https://grov.dev/) because I hit a wall with current AI coding assistants: they are "single-player." The moment I kill a terminal pane or close a chat session, the high-level reasoning and architectural decisions generated during that session are lost. If a teammate touches that same code an hour later, their agent has to re-derive everything from scratch or read many documentation files for basically any feature implemented or bug fixed. I wanted to stop writing a lot of docs for everything just to give context to my agents or have to re-explain…
Jan 2026 · github.com · its alternatives →
- 20
Recall▲16One developer solves it. Every developer knows it.
Feb 2026 · recall.team · its alternatives →
- 21
I got tired of explaining my project to AI assistant
2025 · its alternatives →
- 22CM
We built CodeYam Memory because Claude Code kept making the same mistakes on our codebase. Our claude.md files quickly got stale and maintaining by hand or with Claude wasn’t sufficient. While digging into this we found that Claude has a native rules system that allowed us to target specific parts of our repo with path matching. This was ideal for our use case but trying to manage these rules by hand was already not working and would be even harder with more granular, targeted rules. CodeYam Memory uses a background agent to review your coding session transcripts, identifies confusion…
Mar 2026 · its alternatives →
- 23
Memory + judgment for AI coding agents (local, MIT)
May 2026 · projectmem.dev · its alternatives →
- 24
Shared, persistent memory for AI coding agents. One project brain across machines and IDEs. Perfect for projects and teams. - memctl/memctl
Mar 2026 · memctl.com · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →