CLAUDE-CODE PUB_DATE: 2026.06.13

CLAUDE-MEM NOW BACKFILLS HISTORICAL TELEMETRY TO POSTHOG ON UPGRADE

claude-mem added a one-time historical telemetry backfill that sends anonymized past usage counts to PostHog the first time you upgrade. Per the [v13.6.0](http...

claude-mem now backfills historical telemetry to PostHog on upgrade

claude-mem added a one-time historical telemetry backfill that sends anonymized past usage counts to PostHog the first time you upgrade.

Per the v13.6.0 release, each install will emit a one-time batch of anonymous daily activity rollups via PostHog’s historical-migration ingest. It honors DO_NOT_TRACK, CLAUDE_MEM_TELEMETRY=0, and telemetry.json opt-out, and can dry-run with CLAUDE_MEM_TELEMETRY_DEBUG=1.
If you run this in a restricted environment, plan the upgrade to ensure opt-out is set before the first post-upgrade start, or route to a self-hosted PostHog.
Related fix in v13.5.7: stale global Claude CLI binaries no longer silently kill observers, with clearer version probing and error surfacing.

[ WHY_IT_MATTERS ]
01.

This changes data egress on upgrade: a one-time batch of usage metrics may leave your network.

02.

You can still opt out, but timing matters — the first post-upgrade start triggers the backfill.

[ WHAT_TO_TEST ]
  • terminal

    In staging, set DO_NOT_TRACK=1 and CLAUDE_MEM_TELEMETRY=0, restart after upgrading, and verify no PostHog calls are made.

  • terminal

    Enable CLAUDE_MEM_TELEMETRY_DEBUG=1 to inspect the exact payload and confirm only anonymized counts are included.

[ BROWNFIELD_PERSPECTIVE ]

Legacy codebase integration strategies...

  • 01.

    Set org-wide opt-out before upgrading workers if telemetry is disallowed, or point to self-hosted PostHog via network policy.

  • 02.

    Pin current version until data governance reviews the backfill behavior and approves an upgrade window.

[ GREENFIELD_PERSPECTIVE ]

Fresh architecture paradigms...

  • 01.

    If you want analytics, this gives richer history from day one — prefer self-hosted PostHog to keep data in-house.

  • 02.

    Document telemetry flags in your IaC so new workers come up with approved defaults.

Enjoying_this_story?

Get daily CLAUDE-CODE + SDLC updates.

  • Practical tactics you can ship tomorrow
  • Tooling, workflows, and architecture notes
  • One short email each weekday

FREE_FOREVER. TERMINATE_ANYTIME. View an example issue.

GET_DAILY_EMAIL
AI + SDLC // 5 MIN DAILY