claude-mem Hits 98.3k Stars, but Its Installer Asks for a cmem.ai Login and the README Never Says What Cloud Sync Uploads

The claude-mem repository on GitHub shows 98.3k stars and version 13.34.2, and its installer sends users to a cmem.ai sign-in unless they opt out. The README says cloud sync backs memories up to cmem.ai. It does not say what that upload contains.

Alex Newman, who runs the account @thedotmack, licenses the plugin under Apache 2.0. It records what a coding agent does in a session, summarises it, and feeds the summary into later sessions. The page lists support for Claude Code, OpenClaw, Codex, Gemini and Copilot.

What claude-mem 13.34.2 stores, and where

A local SQLite database holds sessions, observations and summaries, and a Chroma vector database handles search. Settings live in ~/.claude-mem/settings.json. The README does not name a path for the SQLite file or the Chroma store.

Users can keep content out with <private> tags. Requirements are Node.js 20.0.0 or higher, with Bun and uv installed automatically if missing.

What the cmem.ai sign-in does

Running npx claude-mem install asks the user to sign in through the browser with an email magic link. The README says signing in "provisions a memory key for your account". Setting CLAUDE_MEM_ONLINE_OPTIN=false, or running in a non-interactive shell, lets the installer finish without any account step.

The cmem.ai site lists the local engine as free and CMEM Pro at "$30/month" after a 30-day trial. Cloud sync and hosted observation sit under Pro. The site says "synced data is also stored by CMEM", and it does not describe encryption. It points to a separate privacy page, whose contents were not retrieved.

Three open issues worth reading first

Issue	Opened	What the reporter says
#4131	Sep 19	Help for --runtime server implies self-hosting, but the install opened a cmem.ai login and timed out over headless SSH
#4430	Oct 5	A version-bump skill tells an agent to read the npm token in ~/.npmrc and publish without confirmation
#4580	Oct 7	Observations captured during a provider quota cooldown are lost if the worker restarts first

All three were open on October 8. Issue #4430 was opened by a user named omeridel against v13.30.1. That issue says the skill ships in the npm package, which it puts at roughly 69k monthly downloaders, and a linked pull request, #4575, is also open. No maintainer comment was visible on #4430 or #4131.

These are one reporter's accounts of the code, not findings I reproduced.

The CMEM token section

The README carries a section on CMEM, a token. In its words: "CMEM is a token created by a 3rd party but officially embraced by the creator of Claude-Mem (Alex Newman, @thedotmack)." It lists an "Official BASE CA".

The token has no function in the software. It is worth knowing about because the same README that tells users how to install a tool holding their agent's session history also points them at a tradeable asset.

What a user of 13.34.2 should decide

Anyone keeping the default install should know the sign-in step exists and can be skipped. Anyone on a server or CI machine should note issue #4131, since the interactive login timed out for that reporter.

Stars measure attention here. Of the 33 open issues listed, several concern the background worker and its child processes, such as #4563, where disabling Chroma did not stop it from being launched. Pull requests stood at 78.

For another agent tool with an unanswered README question, see the docker agent runner. A second repository of the same kind is REA.