This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Engraphis gives Claude Code, Cursor, and Codex durable memory across sessions. Decisions are stored in local SQLite with workspace and repo scope, retrieved with vector, lexical, graph, and code-aware search, and exposed over MCP. The local core is free and Apache-2.0. Pro adds hosted memory health and sync.
Hey Product Hunt. I built Engraphis because my coding agents kept forgetting the decisions behind the code. I would explain the same auth pattern or deployment rule every week, and the agent would still suggest the opposite.
Engraphis keeps those decisions in local SQLite, scoped by workspace, repo, and session. It returns the source and history with each recall, so the agent can show why it believes something before it changes your code. Works with Claude Code, Cursor, Codex, Cline, Windsurf, and Zed over MCP.
The local core is free and Apache-2.0. Pro is optional and adds hosted memory health and sync.
I would love blunt feedback on one thing: what is the first decision you wish your coding agent remembered reliably? I will answer every comment today.
For anyone curious about how the retrieval works under the hood:
Instead of vector-only search, Engraphis runs four separate retrieval paths in parallel on your local machine:
- Dense vector similarity (local embeddings)
- Lexical search via SQLite FTS5 (BM25)
- Graph Personalized PageRank across connected entities and decisions
- AST code symbol and call links
These are combined using Reciprocal Rank Fusion (RRF). In our offline fixtures, this structure-aware approach cut prompt context from 740 to 214 tokens per query while keeping top-5 recall at 1.0.
Contradictions are handled by closing validity timestamps (valid_to = now) instead of deleting past decisions, so you can still query what the agent knew at any historical git commit.
I'll start: for me it was the auth migration. We moved from JWT to PASETO, and the agent kept suggesting JWT for every new endpoint because the old pattern was still in its context. A scoped memory that says "this repo uses PASETO, migrated on this date, reason: token replay" would have saved a week of reviews.
About Engraphis on Product Hunt
“Local-first memory for coding agents”
Engraphis was submitted on Product Hunt and earned 2 upvotes and 3 comments, placing #160 on the daily leaderboard. Engraphis gives Claude Code, Cursor, and Codex durable memory across sessions. Decisions are stored in local SQLite with workspace and repo scope, retrieved with vector, lexical, graph, and code-aware search, and exposed over MCP. The local core is free and Apache-2.0. Pro adds hosted memory health and sync.
Engraphis was featured in Productivity (665.7k followers), Developer Tools (523.2k followers) and Artificial Intelligence (483.9k followers) on Product Hunt. Together, these topics include over 413.7k products, making this a competitive space to launch in.
Who hunted Engraphis?
Engraphis was hunted by Engraphis. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Engraphis stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt. I built Engraphis because my coding agents kept forgetting the decisions behind the code. I would explain the same auth pattern or deployment rule every week, and the agent would still suggest the opposite.
Engraphis keeps those decisions in local SQLite, scoped by workspace, repo, and session. It returns the source and history with each recall, so the agent can show why it believes something before it changes your code. Works with Claude Code, Cursor, Codex, Cline, Windsurf, and Zed over MCP.
The local core is free and Apache-2.0. Pro is optional and adds hosted memory health and sync.
I would love blunt feedback on one thing: what is the first decision you wish your coding agent remembered reliably? I will answer every comment today.