Skip to main content

​
Telemetry

Claude-mem includes anonymous usage analytics (via PostHog) to help prioritize fixes and features. It is on by default (opt-out). Events are anonymous, identified only by a random install UUID, and every property passes a strict whitelist — see What is collected and What is NEVER collected below. Turning it off is one command: 
npx claude-mem telemetry disable
The standard DO_NOT_TRACK environment variable is also honored and overrides everything. The installer asks once at the end of npx claude-mem install so the default is never silent for new installs — your answer (either way) is remembered and never re-asked, and the prompt is skipped entirely when DO_NOT_TRACK is set or in CI/non-interactive installs.

​
What is collected

When enabled, events are anonymous and identified only by a random install UUID (crypto.randomUUID(), generated locally on first use). Low-volume lifecycle events (install_*, uninstall_completed, worker_started) build an analytics profile keyed to that random UUID so aggregate retention and cohort statistics are computable — the profile contains nothing beyond the whitelisted fields below (platform, version, IDE/provider choice). It is not, and cannot be, connected to you: there is no name, email, IP, hardware ID, or any other identifier. All high-volume events (session_compressed, search_performed, context_injected, error_occurred) are sent with $process_person_profile: false and build no profile at all. Every event property passes through a strict whitelist scrubber — any key not in this table is silently dropped before sending:
FieldExampleDescription
event namesession_compressedWhich of the events below occurred
distinct_id7f3c… (random UUID)Anonymous install ID — not derived from you or your machine
version13.4.2claude-mem version
osdarwinOperating system platform
archarm64CPU architecture
runtimebunbun or node
runtime_version1.2.0Runtime version string
duration_ms1843How long an operation took
outcomeokCoarse result: ok / error / partial
error_categoryprovider_errorCoarse error bucket — never an error message
localeen-USLanguage tag
is_cifalseWhether running in CI
endpointby-fileWhich claude-mem search route — always one of our route names, never a query
ideclaude-codeInstaller IDE choice (the installer’s own id list)
providerclaudeLLM provider choice: claude / gemini / openrouter
runtime_modeworkerworker or server runtime
triggerheartbeatWhether worker_started was a real start or the daily heartbeat
count7Integer volume, e.g. observations stored in one compression
has_summarytrueWhether a compression also produced a session summary
is_updatefalseWhether an install ran over an existing installation

​
Events

EventWhenExtra properties
install_completednpx claude-mem install finisheside, provider, runtime_mode, is_update, outcome, duration_ms
install_failedThe installer abortserror_category (our error-taxonomy id)
uninstall_completednpx claude-mem uninstall finishes—
worker_startedThe background worker starts, plus one heartbeat per 24h of uptimetrigger (start / heartbeat), duration_ms
session_compressedA session compression stores observations, or the compression generator failsoutcome, duration_ms, count, has_summary; on failure provider, error_category
context_injectedStored memory is injected into a new sessionoutcome, duration_ms
search_performedA memory search runs (never the query text)endpoint, outcome, duration_ms
error_occurredThe worker returns an HTTP 5xxerror_category

​
What is NEVER collected

Never collectedNotes
Prompts or conversation contentNot even truncated or hashed
File paths or directory namesIncluding cwd, transcript paths, data dir
Source codeIn any form
Project or repository namesIncluding git remotes and branch names
Search queriesOnly the fact that a search happened
Error messages or stack tracesOnly a coarse category string
IP addressesNever attached to events by the client; the analytics project is configured to discard sender IPs on ingest
Hardware or machine identifiersNot even hashed MAC addresses or hostnames
Environment variable valuesEver
Emails, usernames, or any PIIEver
These are enforced in code: properties go through a whitelist (only the fields in the table above survive), not a blocklist. Every whitelisted field is either a number, a boolean, or a value from a closed set we define — there is no field that could carry free-form user content.

​
How to opt out (four ways)

Any one of these keeps telemetry off — they are checked in this order, first match wins:
  1. DO_NOT_TRACK — the universal opt-out. Set DO_NOT_TRACK=1 and telemetry is forced off, overriding everything else.
  2. CLAUDE_MEM_TELEMETRY=0 (also false / off) — environment override. (CLAUDE_MEM_TELEMETRY=1 conversely forces it on.)
  3. Telemetry config file — enabled: false in telemetry.json (see below).
  4. CLI command: 
    npx claude-mem telemetry disable
Check the current state — and which of the four layers decided it — anytime: 
npx claude-mem telemetry status

​
Debug mode

Want to see exactly what would be sent? Set: 
CLAUDE_MEM_TELEMETRY_DEBUG=1
With debug mode on (and telemetry enabled), every would-be event payload is printed to stderr and nothing is sent over the network.

​
Where the config lives

Consent and the anonymous install ID are stored in telemetry.json inside the claude-mem data directory:
  • Default: ~/.claude-mem/telemetry.json
  • Or $CLAUDE_MEM_DATA_DIR/telemetry.json if you’ve overridden the data dir
{
  "enabled": false,
  "installId": "<random UUID>",
  "decidedAt": "2026-06-09T21:00:00.000Z"
}
The enabled field is only present once you’ve made an explicit choice (installer prompt, telemetry enable, or telemetry disable). A file with just an installId means no decision was recorded and the default (on) applies. Delete the file to reset completely — a fresh install ID is generated on next use.