2026-10-13T03:45:49Z
The client doesn’t send Copilot telemetry, such as an unsupported or third-party editor.
Copilot & Github
The client changed how it sends telemetry, as with the Copilot SDK change above. The client doesn’t send Copilot telemetry, such as an unsupported or third-party editor. The IDE or Copilot extension is out of date and doesn’t send the events that metrics rely on. blog/changelog/2026-10-12-client-telemetry-user-attribution-and-configurable-capture">Client telemetry user attribution and configurable capture</a> appeared first on <a href="https://github. The post Client telemetry user attribution and configurable capture appeared first on The GitHub Blog. blog/changelog/2026-10-06-update-your-ide-to-restore-agent-activity-in-copilot-usage-metrics">Update your IDE to restore agent activity in Copilot usage metrics</a> appeared first on <a href="https://github. identity setting adds three…</p>
<p>The post <a href="https://github. blog/changelog/2026-10-12-push-attribution-public-preview">Push attribution for commits in limited public preview</a> appeared first on <a href="https://github. blog/changelog/2026-09-01-set-an-expiration-date-for-individual-user-budgets">Set an expiration date for individual user budgets</a> appeared first on <a href="https://github. <p>If your Copilot usage metrics have shown agent activity or agent lines of code falling while Copilot usage kept growing, we’ve found the cause, and a fix is rolling out…</p> <p>The post <a href="https://github. The post Update your IDE to restore agent activity in Copilot usage metrics appeared first on The GitHub Blog. The post Push attribution for commits in limited public preview appeared first on The GitHub Blog. The user then falls…</p> <p>The post <a href="https://github. The post Set an expiration date for individual user budgets appeared first on The GitHub Blog. identity setting adds three attributes to OpenTelemetry (OTel) data: user. Commit author…</p> <p>The post <a href="https://github. Push attribution is available now as a limited public preview for GitHub Enterprise customers. Once developers update, their agent activity is counted again in the Copilot usage metrics dashboard and API. <p>You can now set an optional expiration date on an individual user budget, and GitHub removes the budget on that date. You can now set an optional expiration date on an individual user budget, and GitHub removes the budget on that date. If your Copilot usage metrics have shown agent activity or agent lines of code falling while Copilot usage kept growing, we’ve found the cause, and a fix is rolling out to each IDE. Set an expiration date in your billing settings, or use the expires_at field in the Budgets REST API when you create or update a budget. Update your IDE Agent activity is counted again once developers are on these versions. This issue only changed how agent activity was attributed in usage metrics, not what you were charged. Until then, their agent interactions and agent lines of code (e. in the Copilot usage metrics documentation. When you create or edit an individual user budget, you can choose: No expiration, which is the default and matches current behavior. Learn more about setting up budgets and the Budgets REST API. When your reports and other Copilot data disagree, the gap is usually on the client side: Telemetry is turned off in the IDE, so no detailed activity is sent. Usage metrics now use server-side data to count active users that client telemetry misses and to identify the IDE for those users, and we’re continuing to expand where server-side data can fill in. Why client-side metrics can differ from other Copilot data Most detailed usage metrics (e. GitHub also records server-side data when Copilot handles a request. To learn how usage metrics combine client-side and server-side telemetry, see Which usage is included? This will clear up as developers update those clients, but earlier Copilot CLI metrics can’t be corrected, because that activity can’t be separated from real Copilot CLI use. Most of that activity was left out of reports, and some was counted as Copilot CLI activity. Copilot CLI metrics may be inflated, because some activity from other SDK-based clients was counted as Copilot CLI activity. Only IDE versions that use the Copilot SDK for agent mode are affected. Several IDEs recently moved Copilot agent sessions to the Copilot SDK. If your developers are on an affected version, update as soon as the fixed version is available, because their activity can’t be recovered later. Copilot CLI users don’t need to update. Expiration dates are available for the GitHub Copilot Business and Copilot Enterprise plans. 11 Release GitHub Enterprise Server 3. 21 Release The new GitHub Copilot experience in Slack collaboration tools copilot . 21 Release Shared agentic work with GitHub Copilot in Microsoft Teams collaboration tools copilot . We’re steadily reducing how much your reports depend on client telemetry. Those sessions didn’t identify which IDE they came from, so usage metrics couldn’t attribute them correctly. Activity from affected IDE versions doesn’t identify which IDE it came from, so it can’t be attributed after the fact. A network proxy or firewall blocks the Copilot telemetry endpoint. Keep IDE telemetry enabled and allow the Copilot telemetry endpoint through proxies and firewalls. The user then falls back to the next budget that applies to them (i. This applies to enterprise, organization, and user reports, for both 1-day and 28-day reports. To learn more, see the enterprise managed settings reference and monitor agent usage with OpenTelemetry. The most reliable way to keep your metrics complete is to manage your developers’ environments: Keep IDEs and Copilot extensions current. To use this option, select Close content authored by this user in the block dialog. Close all open contributions authored by a blocked user - GitHub Changelog Skip to content Skip to sidebar / Blog Try GitHub Copilot app Attend GitHub Universe Back to changelog Improvement August 27, 2026 • 1 minute read Close all open contributions authored by a blocked user You can now automatically close all open issues, discussions, and pull requests authored by a user when you block them from your personal account or organization. Fine-grained capture controls are available in Copilot CLI, the GitHub Copilot app, and VS Code sessions using Agent Host. You can now automatically close all open issues, discussions, and pull requests authored by a user when you block them from your personal account or organization. name: The authenticated Copilot account name, currently the GitHub login. The fix is available now in Visual Studio Code. 0 and later Available now Visual Studio 18. In per-user reports, totals_by_ide includes last_known_ide_version and last_known_plugin_version for each user. , feature, language, model, and lines of code breakdowns) come from telemetry that each IDE sends. , their cost center per-user budget or otherwise your universal budget). Some detail, such as lines of code and accepted suggestions, can only come from the editor, so client-side gaps won’t disappear entirely. You’ll see it whenever you block a user, including from an issue or pull request comment, or from Settings → Moderation → Blocked users. <p>GitHub now durably records the authenticated user who pushed each commit and surfaces that pusher identity in the UI and API alongside the existing author and committer fields. GitHub now durably records the authenticated user who pushed each commit and surfaces that pusher identity in the UI and API alongside the existing author and committer fields. This release adds durable, per-commit pusher attribution alongside the author and committer metadata. With this release: Every commit pushed to a repository now has a durable, authenticated pusher identity attached to it, independent of whatever the author and committer metadata claims. Commit author and committer fields are just strings that the pushing client supplies, so anyone with write access to a repository can set them to any name and email they choose. To enforce stricter identity requirements on a repository, add the new Committer must match pusher rule to a ruleset. Use your device management tooling to enforce minimum versions where you can. <p>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. 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. You can do this because the pusher identity is now visible wherever commits are shown instead. You can use the pusher identity to spot-check suspicious activity or speed up security investigations instead of relying on unverified metadata. Join the discussion within GitHub Community. The existing captureContent setting remains available as a legacy shorthand for the five content classes, but it never enables identity. Identity capture is off by default and remains separate from the existing pseudonymous user identifier. Every capture class is off by default. Enable only the classes required for your audit use case and send them to an approved collection endpoint. This closes a path for commit identity spoofing. Explicit managed values take precedence over local settings, SDK configuration, and environment variables. Administrators can also independently control five additional capture classes: prompts: User, system, and developer prompts and supported input context.2026 & Expected
Other IDEs will receive it in upcoming releases, which we expect to finish rolling out by November 2026. 12 Not yet released, expected in October 2026 JetBrains IDEs Next plugin release Not yet released, expected by late October 2026 Eclipse Next plugin release Not yet released, expected by November 2026 Xcode Next plugin release Not yet released, expected by November 2026 We’ll add each version to the supported IDEs in the docs as it ships.
Tool & Results
Prompt, tool, and policy capture can include source code, file contents, commands, tool results, and workspace or user-profile paths. toolOutput: Tool results and execution-error details.
Learn more about setting up budgets and the Budgets REST API.
Read the original sources cited in the article for the full material.
Frequently asked questions
**What does the collected research say about Client telemetry user attribution and configurable capture <p>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. The telemetry.capture.identity setting adds three…</p>
<p>The post <a href="https://github.blog/changelog/2026-10-12-client-telemetry-user-attribution-and-configurable-capture">Client telemetry user attribution and configurable capture</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>?** <p>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.What are the key details from GitHub Changelog?
<p>GitHub now durably records the authenticated user who pushed each commit and surfaces that pusher identity in the UI and API alongside the existing author and committer fields.