What
The OTLP (OpenTelemetry protocol) resource-attribute builder used for telemetry now adds a user.groups attribute, a comma-joined list of the session's group names, alongside the existing enduser.id and user.email attributes.
The attribute is only added if none of the group names contain a comma or an equals sign, and if the URL-encoded joined string is 255 characters or less; otherwise it's left out.
Why
This lets telemetry and observability tooling see which groups a user belongs to, while avoiding malformed or oversized attribute values.
Names in the bundleuser.groups
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Claude apps gateway configuration touched a line naming user.groups after this was published.
In sessions signed in through `/login`, the CLI stamps each export with the authenticated user's identity, read from the gateway-issued JWT: the `user.id`, `user.email`, and `user.groups` attributes. Per-developer cost and usage attributio…claude-apps-gateway-config see the edit
Confirmed since
Anthropic's documentation has since written up user.groups, on Claude apps gateway configuration.
[Claude Desktop](#claude-desktop-overlay) and Cowork sessions signed in through the gateway stamp their telemetry with `user.email` and `user.groups` alongside `enduser.id`, so you can cover terminal, Desktop, and Cowork usage with one que…claude-apps-gateway-config see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up user.groups, on Claude apps gateway configuration.
Anthropic's release notes agree
Added user.email and user.groups to the telemetry Claude Desktop and Cowork send through a Claude apps gateway, matching terminal sessions