Copilot telemetry can attribute agent activity to a user without capturing prompts, with five content classes each off by default
Enterprise admins get separate switches for who did something and what was said, in OpenTelemetry data from Copilot CLI, the Copilot app and VS Code.
// Key points
- telemetry.capture.identity adds user.name (the GitHub login), process.user.name (the local OS account) and host.name to OTel data; it is off by default.
- Prompts, responses, tool arguments, tool output and policy detail can each be captured independently, and all five are off by default.
- Explicit managed values take precedence over local settings, SDK configuration and environment variables.
Builder's takeSeparating identity from content is the right default: you can answer “whose agent ran this command” in an incident without storing everyone’s prompts. I’d enable identity plus tool arguments for audit, keep prompts and responses off, and apply the same split to the agent logs in our own products.
// Background · from #Coding agents
Full timeline →- Oct 14 Gemini 4 Argon is generally available in GitHub Copilot, billed at provider list price and on by default for Business and Enterprise unless admins turn it off
- Oct 14 Copilot enterprise settings can force a fresh policy at startup and fail closed, and the sandbox key now enforces a minimum client version
- Oct 12 Copilot weekly releases: VS Code 1.141 shows agent sessions side by side in a grid and cleans up idle worktrees by disk usage