I kept running into the same problem: every Claude Code session starts from scratch. It doesn’t know my project, my preferences, or what we discussed yesterday. So I built https://mengram.io/ — a memory layer that plugs into Claude Code via hooks. Setup: pip install mengram-ai export MENGRAM_API_KEY=om-your-key # free at mengram.io mengram hook install What happens after that: Session start → loads your cognitive profile (Claude knows who you are, your stack, preferences) Every prompt → searches memory for relevant context and injects it before Claude responds After response → saves the conversation in the background You don’t do anything manually. Memory builds up over time and Claude gets better at understanding your project. How it works under the hood: 3 Claude Code hooks: SessionStart → calls mengram auto-context → loads profile via GET /v1/profile UserPromptSubmit → calls mengram auto-recall → semantic search, returns additionalContext Stop → calls mengram auto-save → sends conversation to POST /v1/add (async, background) All hooks are non-blocking. If the API is slow or down, Claude Code continues normally. Also works with any MCP client (Claude Desktop, Cursor, Windsurf, OpenCode) — 29 tools via MCP server. Website: https://mengram.io/ Docs: https://docs.mengram.io/ GitHub: https://github.com/alibaizhanov/mengram Disclosure: I’m the creator of Mengram. It’s open source with a free tier. Posting because I think it solves a real pain point for Claude Code users. Happy to answer questions. submitted by /u/No_Advertising2536
Originally posted by u/No_Advertising2536 on r/ClaudeCode