graphmind — I gave Claude persistent architectural memory across all my coding sessions
The problem I kept hitting: every Claude Code session starts from zero. Claude re-reads files, rediscovers architecture, asks questions you answered last week. On a large codebase this is brutal — you spend more time re-explaining context than actually building.
graphmind solves this with two things working together:
Persistent memory — Claude automatically saves and recalls architectural decisions, patterns, and conventions across sessions. Not just "remember this fact" but structured memory: decisions, patterns, conventions, known bugs, business context. It's recalled automatically at each prompt — you never need to ask "do you remember X?".
Structural context on demand — instead of dumping raw files into the context, graphmind gives Claude a precise, ranked answer: the right symbols, their callers/callees, and the structural relationships that matter.
The token difference is significant. On a real 31k-symbol codebase:
- grep dumps ~1.4M tokens of noise per search
- graphmind returns ~260 tokens of signal
- That's a 5,700x reduction — roughly the entire context window saved per session
Everything runs 100% locally. No cloud. No telemetry. Memory stored as plain JSONL in ~/.graphmind/memory/.
Built this while working across 11 repos. Happy to answer questions about the memory architecture specifically.