Starstruk Logo MarkStarstruk

v13.5.4

HumanSignal/label-studiov13.5.4Jun 10, 2026by thedotmack

AI Summary

This release fixes telemetry geolocation by allowing PostHog to derive coarse location from request IP instead of suppressing it. The IP promise remains unchanged - raw IP addresses are never attached to events.

Key Highlights

  • Closed ~98.5% 'unknown location' gap in telemetry
  • Client now passes disableGeoip: false to PostHog
  • Ingest-side GeoIP now derives coarse location from request IP
  • Telemetry docs and consent screen now disclose ingest-derived coarse location
  • New regression test asserts PostHog client is constructed with disableGeoip: false

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)