# GitHub — Client telemetry user attribution and configurable capture

- Company: GitHub (github.com)
- Announced: 2026-10-12T22:38:00+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://github.blog/changelog/2026-10-12-client-telemetry-user-attribution-and-configurable-capture
- Record: https://forck.live/items/20149-client-telemetry-user-attribution-and-configurable-capture
- Subject: Copilot
- Models affected: GitHub Copilot

GitHub added a telemetry setting that lets enterprise administrators attribute Copilot activity to a user without collecting prompts, responses, or tool content. The telemetry.capture.identity setting adds user.name, process.user.name, and host.name attributes to OpenTelemetry data, and is off by default. Administrators can also independently control five additional capture classes — prompts, responses, toolArguments, toolOutput, and policyDetail — each off by default, with explicit managed values taking precedence over local settings.

## Evidence

Verbatim from https://github.blog/changelog/2026-10-12-client-telemetry-user-attribution-and-configurable-capture:

> Enterprise administrators can now use telemetry in managed settings to attribute GitHub Copilot activity to a user without collecting their prompts, responses, or tool content.

---

Record: https://forck.live/items/20149-client-telemetry-user-attribution-and-configurable-capture
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md