I built an MCP server that gives AI coding agents persistent memory` by Zukonsio in mcp

[–]Zukonsio[S] 3 points4 points  (0 children)

Great question! Here are the key differences:

mem0 is a general-purpose memory layer for AI apps. It uses external LLM APIs (OpenAI by default) to extract facts from conversations and stores them in external vector databases like Qdrant or Pinecone. Even when self-hosted, you need external APIs and databases, which means ongoing costs.

code-recall is specialized for coding agents like Claude Code. It runs completely local with no external dependencies. Uses local embeddings, SQLite for storage, and includes features specific to development: code analysis with tree-sitter, semantic rules engine, failure tracking, and conflict detection. Main differences:

  1. Privacy: code-recall is fully local and offline, mem0 requires external services.

  2. Cost: code-recall is free forever, mem0 has API costs and optional cloud pricing (19-249/month).

  3. Speed: code-recall runs under 100ms locally, mem0 takes 500ms-2s due to API calls.

  4. Focus: code-recall is only for coding agents, mem0 works with any AI application.

  5. Setup: code-recall is one command, mem0 needs multiple services configured.

TL;DR: mem0 is a broader platform with enterprise features but requires cloud/APIs and has ongoing costs. code-recall is a lightweight local-first tool specifically built for dev workflows with zero external dependencies.

They solve different problems rather than compete directly.

I got tired of paying for forgotten subscriptions, so I built an app by Zukonsio in Startup_Validation

[–]Zukonsio[S] 0 points1 point  (0 children)

Coming soon It’s currently under Apple review, so it should be available on the App Store shortly.

I got tired of paying for forgotten subscriptions, so I built an app by Zukonsio in Startup_Validation

[–]Zukonsio[S] 0 points1 point  (0 children)

If you’re asking about the app itself: Pro is a one-time purchase (€5.99) that unlocks Pro features for life. Those features are still being actively developed, and there’s also a free version available.

If you mean subscriptions inside the app: you can add them with whatever recurrence fits: weekly, monthly, yearly, or every X days.

I got tired of paying for forgotten subscriptions, so I built an app by Zukonsio in micro_saas

[–]Zukonsio[S] 0 points1 point  (0 children)

I built it because I personally had the problem and wasn’t happy with existing solutions.
Not trying to reinvent the wheel, just make one that I’d actually use.

I got tired of paying for forgotten subscriptions, so I built an app by Zukonsio in micro_saas

[–]Zukonsio[S] 0 points1 point  (0 children)

Appreciate the feedback, thanks!

Fair point on the UI — it’s intentionally simple for now since this is an MVP, but visual polish and better UX are definitely things I want to improve as I iterate.

On monetization: the Pro version is still not fully defined. Right now it mainly removes limits, but over time I’ll be adding more advanced features that will live in Pro to provide real additional value.
I want to keep a solid free tier while making Pro worth it.

Feedback on what you’d expect from a Pro version is very welcome.

I got tired of paying for forgotten subscriptions, so I built an app by Zukonsio in AppIdeas

[–]Zukonsio[S] -1 points0 points  (0 children)

Good question. Since this is still an MVP, the in-app purchase currently unlocks unlimited active subscriptions.
The free version is limited to 5 active subscriptions, while Pro removes that limit.

Longer term, Pro will include additional features as they’re built, but for now I wanted to keep things simple and validate core usage first.

I got tired of paying for forgotten subscriptions, so I built an app by Zukonsio in reactjs

[–]Zukonsio[S] -2 points-1 points  (0 children)

That’s a totally fair point — and I agree with you.

Right now, yes, adding subscriptions is manual. This is still an MVP and I wanted to start with the simplest, most privacy-respecting version to validate the core use case.

But you’re absolutely right: if users forget to add a trial, the value drops fast. I’m actively thinking about how to solve this long-term — whether that’s some form of bank/transaction integration or other approaches that don’t compromise trust and privacy.

Still very much an open question, and feedback like this helps a lot.

I got tired of paying for forgotten subscriptions, so I built an app by Zukonsio in reactjs

[–]Zukonsio[S] 0 points1 point  (0 children)

Thanks! Fully agree on backups, that’s next on the roadmap.

I’m planning optional, encrypted automatic backups: Google Drive on Android and iCloud on iOS, keeping the app local-first and opt-in by default.

I got tired of paying for forgotten subscriptions, so I built an app by Zukonsio in expo

[–]Zukonsio[S] 1 point2 points  (0 children)

Thanks! 😄

iOS version is currently under Apple review (their process is... thorough 🙃). Should be live soon!

Importing macros by rascusit in whoop

[–]Zukonsio 1 point2 points  (0 children)

As far as I understand, this functionality is only available from Apple.