Follow Discord
Sweep 30 Oct 2026 · 21:36Z Build v2.1.315 533 read Stable v2.1.308 Latest v2.1.314 Next v2.1.315 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.315 ·

Analytics events are stamped with the account that produced them and filtered by it

Claude Code's own analytics events now carry a principal stamp, and events recorded under a different account are no longer sent

Group of 3 Under the hood Bug Fixes
JSON All of v2.1.315
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Bug FixesKind: in v2.1.315,
Bug FixesSection of the release

What

Claude Code sends its own usage analytics to Anthropic. Each event is now tied to the principal, meaning the signed-in identity, that produced it:

  • Both ways of recording an event now attach a value worked out from the event name, as principalStamp (principal_stamp when sent). Events queued before analytics has started keep their stamp.
  • When sending, events stamped with a different principal from the current one are dropped. Events are also dropped by HIPAA-style checks, a set of safety events was added, and some internal events are removed when the data is cleaned up.
  • The stamp is passed along with every event that is sent.
  • In some cases the identity sent with events is built only from the environment variables CLAUDE_CODE_ACCOUNT_UUID, CLAUDE_CODE_ORGANIZATION_UUID, CLAUDE_CODE_SUBSCRIPTION_TYPE and CLAUDE_CODE_RATE_LIMIT_TIER, instead of the stored account. The device ID falls back to those account and organization IDs.

Why

If you switch accounts, events recorded under one account are no longer sent as if they came from another, so analytics stay tied to the account that produced them.

See this entry in the whole of v2.1.315 →

Feedback