v13.5.4
tremorlabs/tremorv13.5.4Jun 10, 2026by thedotmack
AI Summary
Fixes telemetry geolocation by closing the ~98.5% unknown location gap while maintaining privacy promises about raw IP addresses.
Key Highlights
- PostHog GeoIP now enabled with disableGeoip: false
- Raw IP addresses still never attached to events or stored
- Ingest-derived coarse location (country/region/city) disclosed
- Regression test ensures PostHog client constructed correctly
- Telemetry documentation updated to reflect location features
New Features
- Telemetry GeoIP enabled for worker events
- Ingest-side coarse location derivation from request IP
- Privacy maintained: raw IPs never stored or attached
- New regression test for PostHog client configuration
- Updated consent screen and documentation
Full Release Notes
## Fixed - **Telemetry geolocation: closed the ~98.5% "unknown location" gap.** The posthog-node SDK assumes server deployments and stamps `$geoip_disable: true` on every event by default. claude-mem's worker runs on the user's own machine, so this needlessly suppressed PostHog's ingest-side GeoIP on all worker events (`worker_started`, `session_compressed`, `context_injected`, ā¦). The client now passes `disableGeoip: false`, letting PostHog derive coarse location (country / region / city) at ingestion ā from the request IP, which is then discarded. CLI events (`install_*`) were already unaffected. ## Privacy - No change to the IP promise: raw IP addresses are still **never attached to events by the client and never stored** ā the sender IP is used transiently at ingest for the coarse-location lookup, then discarded. - The telemetry docs (https://docs.claude-mem.ai/telemetry) and the `npx claude-mem telemetry enable` consent screen now disclose the ingest-derived coarse location. ## Tests - New regression test asserts the PostHog client is constructed with `disableGeoip: false` (telemetry suite now 58 tests, all passing). š¤ Generated with [Claude Code](https://claude.com/claude-code)