Why now?

claude-mem gained 1,723 stars in a day and ~78,676 npm downloads last month, and its own topics (mem0, supermemory, chromadb) show agent memory is being actively rebuilt now. The pain — agents forgetting context between sessions — spans Claude Code, Codex, Gemini and Copilot, so the window is before native memory features absorb it.

The gap

It is a library, not a product: no hosted sync, no team sharing, no UI, no billing, 146 open issues. A 0.088 fork ratio against 106k stars and zero HN mentions mean interest is broad but build-on intent and public demand are unproven.

Main competitor

mem0 (with supermemory and Chroma adjacent), plus native memory features inside Claude Code and other agent tools — all named in claude-mem's own topics, confirming direct overlap.

Execution plan

1. Fork claude-mem (Apache-2.0) as a hosted service with managed storage and API keys, removing local SQLite/Chroma setup.
2. Ship a minimal dashboard to browse, search, edit and delete memories per project and per agent — a layer the OSS project lacks.
3. Add cross-agent sync so one memory store serves Claude Code, Codex, Gemini and Copilot, and publish a compatibility matrix.
4. Triage the 146 open issues, fix top install complaints, and launch on Show HN and r/ClaudeAI to convert the 78k monthly npm users.
5. Instrument sessions captured and memories injected from day one so pricing and retention rest on real usage, not stars.

Monetization

Freemium: free self-hosted tier mirroring the OSS project; paid hosted tier per seat or memory volume for sync, shared memory and the dashboard. Paid demand is unproven — the signals show free adoption only, so validate willingness-to-pay in a small hosted beta first.