Starstruk Logo MarkStarstruk

v13.5.0

thedotmack/claude-memv13.5.0Jun 10, 2026by thedotmack

AI Summary

claude-mem introduces anonymous, privacy-hardened usage analytics (PostHog) — the first telemetry in the project, following the standard dev-tool model with opt-out options. The release includes eight tracked events with strict whitelist scrubbing to ensure no sensitive data leaves the user's machine.

Key Highlights

  • Anonymous usage analytics (PostHog) with privacy-first design - on by default, one command to opt out
  • Eight tracked events: install_completed, install_failed, uninstall_completed, worker_started, session_compressed, context_injected, search_performed, error_occurred
  • Strict whitelist scrubber - only numbers, booleans, and predefined values (platform, version, IDE, durations, counts) can leave the machine
  • Multiple opt-out methods: npx claude-mem telemetry disable, DO_NOT_TRACK=1, or CLAUDE_MEM_TELEMETRY=0
  • Install flow improvements with live progress for dependency steps and consent prompt

New Features

  • Anonymous usage analytics (PostHog)
  • npx claude-mem telemetry [status|enable|disable] CLI command
  • Worker shutdown with hard 3s bound telemetry flush
  • Live progress for dependency steps during install
  • Consent prompt at end of install

Full Release Notes

## Anonymous usage analytics (PostHog) — and the v13.5.0 release

claude-mem now ships anonymous, privacy-hardened usage analytics. This is the first release with any telemetry, and it follows the standard dev-tool model (Homebrew, Next.js, Astro): **on by default, one command to opt out, and incapable of carrying your content by construction.**

### What's collected

Eight events (`install_completed`, `install_failed`, `uninstall_completed`, `worker_started`, `session_compressed`, `context_injected`, `search_performed`, `error_occurred`), identified by a random install UUID generated locally. Every property passes a strict whitelist scrubber — only numbers, booleans, and values from closed sets we define (platform, version, IDE choice, durations, counts) can leave your machine.

**Never collected — enforced by whitelist, not blocklist:** prompts or conversation content, file paths, source code, project or repo names, search queries, error messages, IP addresses, hardware identifiers, env values, emails, or any PII.

### Opting out

Any one of these turns it off:

- `npx claude-mem telemetry disable`
- `DO_NOT_TRACK=1` (the universal standard — overrides everything)
- `CLAUDE_MEM_TELEMETRY=0`

`npx claude-mem telemetry status` shows the current state and which setting decided it. The installer asks once at the end of `npx claude-mem install`, and your answer is never re-asked.

Full documentation of every field and event: https://docs.claude-mem.ai/telemetry

### Also in this release

- Install flow: live progress for dependency steps and a consent prompt at the end of install
- `npx claude-mem telemetry [status|enable|disable]` CLI command
- Worker shutdown now flushes telemetry with a hard 3s bound — never delays stop

🤖 Generated with [Claude Code](https://claude.com/claude-code)