Alternatives
Products that do what GraphMind does
Stop re-teaching your AI your codebase.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8RA
Hey HN! I built Retain as the evolution of claude-reflect (github.com/BayramAnnakov/claude-reflect). The original problem: I use Claude Code/Codex daily for coding, plus claude.ai and ChatGPT occasionally. Every conversation contains decisions, corrections, and patterns I forget existed weeks later. I kept re-explaining the same preferences. claude-reflect was a CLI tool that extracted learnings from Claude Code sessions. Retain takes this further with a native macOS app that: - Aggregates conversations from Claude Code, claude.ai, ChatGPT, and Codex CLI - Instant full-text…
Jan 2026 · github.com
- 9
- 10
- 11
- 12
Your AI has your code's text, never its map. Fix that.
Jun 2026 · luuuc.github.io
- 13
An agent that remembers across sessions can keep its memory as curated markdown files, as an auto-mined structured store, or as trained experience.
22d ago · pinglin.tw
- 14
- 15
- 16
Open-source MCP server. #5 on LoCoMo. 100% local. MIT.
May 2026 · totalmemory.dev
- 17
Agents start blind every session. dizz gives them a memory.
Aug 2026 · github.com
- 18SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 19BA
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
- 20SA
I built SpecMind, an open source developer tool for spec driven vibe coding. It keeps architecture and implementation aligned from the first commit instead of letting them drift apart. With AI assistants writing more of our code, projects move faster but architectural consistency is often lost. Each developer or AI can introduce new patterns, and after a few sprints, the structure becomes fragmented. SpecMind helps prevent that by generating and maintaining living architecture specs directly from your code. It works in three steps: 1. analyze – scans your codebase and generates…
Nov 2025 · github.com
- 21
- 22
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →