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).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
MemContinuum — memory for Claude Code
MemContinuim is linking chain of decisions with the codebase
You forget what was decided. The model forgets harder. Most memory tools capture what happened; MemContinuum does something different. - Rationale records what was decided, who decided it, and how that decision changed — then pushes the governing chain into the agent's prompt before it edits the file, so nobody has to remember to look. - Anatomy holds what the code already has — its concepts, owners and boundaries — so it stops being reinvented. - Decisions bind directly to the code they govern.
Hello, colleagues.
I've bitten off something ambitious.
Analyzing the problems surfacing on my own project ShotPorter https://ShotPorter.com, I decided I needed a long-term memory system.
Looking at what already exists, I found nothing that solved my problems, so I built my own. After using it for a while, I decided it was worth polishing and releasing publicly.
It became MemContinuum — long-term decision memory for Claude Code projects. And it is not just another memory system, collecting facts happened and words written.
**The problems it addresses.**
On a long project you forget what was decided about a given question and why. The model forgets harder. Subagents know nothing at all — the orchestrator dispatches them nearly blind onto narrow tasks. The result is reinvention instead of reuse: duplicate implementations, drift, tokens burned re-solving solved problems, and settled questions resurfacing as "wait, why is this written this way?"
**How it differs from the memory systems I looked at:**
- Two layers: ANATOMY - an indexed map of the code, and RATIONALES - decision chains recorded against it — what was decided, **who** decided it, how it changed over time, plus incidents and rejected alternatives with reasons.
- Reading is automatic. Before an agent edits a file, the decision chain governing that path is injected into its prompt. Nobody has to remember to look.
- Writing is unavoidable but not automatic. The agent gets a question it must answer; "nothing to record" is a legitimate answer. It's moderated by judgment, not a scraper dumping everything into a pile by keyword or timestamp.
- One AI writes records — the orchestrator. Subagents and external reviewers (Codex, Grok) propose through an inbox; proposals become records after triage.
- Per project, local, no server. Markdown as the source of truth, SQLite as a disposable index.
Built for coding projects specifically: without indexable code only half the brain works.
Current state: 0.2.0rc4, honestly labelled a release candidate. MIT. Claude Code only for now. The README is long and detailed if you want the full picture.
Feedback of any kind is very welcome.
Besides me, a team of authors worked on this project:
- Claude Code: Fable 5/5.1 as lead engineer and project manager; Opus as inspector; Sonnet as coder; Haiku as tester
- Codex: 5.6 Sol / 6 Astra as reviewer and outside consultant
- Grok 4.6 as second reviewer
https://github.com/krakozavr/Mem...
About MemContinuum — memory for Claude Code on Product Hunt
“MemContinuim is linking chain of decisions with the codebase”
MemContinuum — memory for Claude Code was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #103 on the daily leaderboard. You forget what was decided. The model forgets harder. Most memory tools capture what happened; MemContinuum does something different. - Rationale records what was decided, who decided it, and how that decision changed — then pushes the governing chain into the agent's prompt before it edits the file, so nobody has to remember to look. - Anatomy holds what the code already has — its concepts, owners and boundaries — so it stops being reinvented. - Decisions bind directly to the code they govern.
On the analytics side, MemContinuum — memory for Claude Code competes within Software Engineering, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how MemContinuum — memory for Claude Code performed against the three products that launched closest to it on the same day.
Who hunted MemContinuum — memory for Claude Code?
MemContinuum — memory for Claude Code was hunted by Alex Potemkin. 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.
For a complete overview of MemContinuum — memory for Claude Code including community comment highlights and product details, visit the product overview.
Alex Potemkin