@sarahsimionescuchecks…claude/loving-leavitt-3c8aad → main4 files · +34 −11review: @shamsharoonupdated 5h agoGive every anonymous (unauthenticated / pre-identify) LaunchDarkly context a single shared constant key (ANONYMOUS_CONTEXT_KEY) instead of a unique key per browser/IP/request.
LaunchDarkly bills by unique context key per month (cMAU). Today anonymous contexts each get a unique key:
provider.tsx): anonymous: true with no key → the SDK auto-generates a unique key per browser (cached in localStorage).launchdarkly.ts): key: ip ?? crypto.randomUUID() → a unique key per IP / per request.Per the LaunchDarkly Cost Audit, anonymous contexts are ~50% of our total cMAU (~120k/mo). Collapsing them to one shared key drops that to a single cMAU.
flags.ts — add ANONYMOUS_CONTEXT_KEY constant (plain string, shared by client + server).provider.tsx — set key: ANONYMOUS_CONTEXT_KEY on the initial anonymous context.launchdarkly.ts — replace ip ?? crypto.randomUUID() with ANONYMOUS_CONTEXT_KEY for unauthenticated requests. IP is retained as the ip attribute (doesn't affect billing).docs/feature-flags.md — update the auto-populated context tables + add a cMAU billing note.Percentage rollouts no longer distribute across individual anonymous users — they all receive the same variation. This is acceptable: anonymous contexts only exist momentarily before identify() upgrades them to the real user, and authenticated targeting/rollouts are unaffected.
This addresses one item from the audit (anonymous contexts). The other recommendations (removing the unique_id context kind, dropping project/project_id context kinds) live in the Apollo/platform repo, not here.
🤖 Generated with Claude Code
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| dashboard |  Ready | Preview, Comment | Jun 13, 2026 3:32am |