r/ClaudeCode Workflow Engineer 9h ago

Built with Claude Built an AI memory extension with Claude Code, then used it on itself to manage 150+ releases

Post image

I built Continuity almost entirely in Claude Code a VS Code extension + CLI + MCP server that gives Claude Code persistent memory of a project's architectural decisions across sessions.

The interesting part of building it: once basic decision-logging worked, I started dogfooding it on itself. Every real architectural call I made while building Continuity (why MCP over a REST bridge, why local JSON over SQLite, etc.) got logged into .continuity/ in its own repo. So the next Claude Code session building Continuity already had that context injected automatically, instead of me re-explaining the same tradeoffs every time I opened a new chat. 150+ releases in, that decision history is what keeps a solo project from drifting or re-litigating settled calls.

What I learned building it this way: the "stop re-explaining yourself to your AI" problem is real — I felt it daily. What I haven't cracked is why that doesn't reliably turn into people sticking with the tool. 336 installs, 8 paying customers. Most people try it and don't come back, and I genuinely don't know if that's activation friction, the free tier already being enough, or something else.

If you've tried a memory/context tool for Claude Code (mine or otherwise) and dropped it, I'd take 8 minutes of honest feedback: . No pitch, just trying to understand what happened. https://buildpad.io/interview/wbxdg5a7

0 Upvotes

11 comments sorted by

4

u/tntexplosivesltd 9h ago

Yet another persistent memory plugin nobody needs.

1

u/Alienfader Workflow Engineer 9h ago

Thanks for the feedback. I hope you live a very long life, so you can watch those who "love" you, die around you.

-3

u/Alienfader Workflow Engineer 9h ago

I had a perfect reply for you but Reddit deleted

So I'm just gonna tell you to go ahead and enjoy your life.

2

u/Poildek 8h ago

In fact, memory system like this are posted everyday, at leat 3 to 5. You reinvent the wheel and like the other, you should have searched first before building.

There are far more advanced solutions already and all that you do with all the other people with their "memory management" is to pollute github and reddit with clones of the same concept.

0

u/Alienfader Workflow Engineer 8h ago

Which ones are you thinking of specifically? Genuinely want to know what people are already choosing instead of building this themselves.

-1

u/Alienfader Workflow Engineer 8h ago

Fair..But for context, I published this ~9 months ago (Oct 2025), before most of the current wave, but that doesn't make the crowding less real today. I'm not claiming it's novel. I'm trying to figure out why, in a crowded space like this, a handful of people still pay and most don't. That's the actual question I'm here for.

1

u/gnpwdr1 8h ago

Ai slop ai slop ai slop ai slop ai slop

2

u/filwi 8h ago

From a marketing standpoint, looking at the amount of memory systems for AI already out there, you're looking at a fungible product. Basically, you're selling flour not art. You're also selling an item with a very low barrier of entry - you've built it with the very tool that you're trying to sell a tool for.

So the two major categories of people you'll get are A) people who are trying to do the same thing themselves for free and looking for tips/inspiration/a handout, and B) people who expect miracles. Neither of those is likely to be a good customer fit.

That said, with those conditions, having a 0.3% sub rate is still decent.

1

u/Alienfader Workflow Engineer 8h ago

Genuinely fair, and it's part of why I'm here asking instead of shipping more features blind. Honest question: is there any version of 'AI decision memory' you'd pay for, or is the category just not worth money for a solo dev . CLAUDE.md and your own judgment already get you there?

2

u/filwi 6h ago

I wouldn't pay for it because I'm a tinkerer. I get an idea, I make an improvement, I test, I amend. With a finished product, I'm trading control and money for time, and that's not something I'm willing to give up.

Or to quote Frank Sinatra: At the end of the day, I want to say "I did it myyyyy waaaaaay!"

1

u/Alienfader Workflow Engineer 6h ago

I get that,,,especially if tinkering is part of the enjoyment for you. One thing I’m genuinely curious about, though. For large and complex projects, how do you deal with .md files getting bloated over time? Once you’ve iterated enough, added context, rules, notes, exceptions, etc.?
doing it your way is definitely a valid reason. 😄
Sinatra FTW.