GitHub Copilot Usage Metrics Adds Agent-App Activity
Teams can now separate third-party agent activity such as Claude and Codex in usage reports.
Key takeaways
GitHub announced on August 7, 2026 that the Copilot Usage Metrics API now reports activity from third-party agent apps. Enterprise, organization, enterprise-user, and organization-user reports can expose the activity in one-day and 28-day windows. The new totals_by_3rd_party_agent data includes a stable agent_id and a display name that may change; the identifier should be the join key. This gives administrators a finer view of cost, permissions, and workflow adoption, but it does not automatically explain business value. Start with a read-only sample, reconcile time zones, pagination, and overlapping windows, then associate agent activity with AI credits, members, repositories, and permission changes before changing budgets or access.
# GitHub Copilot Usage Metrics Adds Agent-App Activity
August 9, 2026
On this page
- Direct answer
- Fact sources
- Action guide
- Why it matters
- Impact
- FAQ
- Sources
Direct answer
Use agent_id as the stable key, keep one-day and 28-day windows separate, and reconcile pagination and time zones before connecting agent activity to credits, members, repositories, or permission changes.
Fact sources
GitHub's August 7 changelog adds third-party agent-app activity to Usage Metrics API reports.
The reports cover enterprise, organization, enterprise-user, and organization-user scopes in one-day and 28-day windows.
agent_id is the stable join key; an agent's display name can change.
Five steps to audit agent-app usage
- Confirm token permissions, API version, and report scope with a small sample.
- Store agent_id as the key and keep the display name for presentation.
- Pull one-day and 28-day windows separately; check pagination and time zones.
- Join activity to credits, members, repositories, and permission changes.
- Observe one read-only cycle before adding budget, limit, or disable actions.
Why it matters
As multiple agents enter GitHub workflows, total Copilot usage can hide tool-specific cost and access risk. Stable identifiers and explicit windows make the data auditable.
Impact for ordinary AI users
Teams can explain Claude or Codex activity more precisely, but metrics are not a complete measure of value. Wrong joins, time zones, and permissions can still mislead.
Related tools and tutorials
Account services can support access and quota governance; software and skill-learning pages can support API, logging, and review workflows.
AI software and tool entry points · AI account permissions and cost services · AI skill tutorials and validation methods · AI frontier news overview
FAQ
Why not key on agent_name?
GitHub says display names can change; agent_id is the stable identifier.
Can one-day and 28-day reports be added?
No. They are different windows and adding them can double count.
Can the API disable an agent automatically?
Begin with read-only observation and human approval before designing automated actions.
Source links
- GitHub Changelog: Usage Metrics API adds agent app activity (2026-08-07)
- GitHub REST API: Copilot usage metrics
- GitHub reference: Agent app metrics fields
What this means for everyday users
Keep agent_id, window, credits, members, repositories, and permission changes in the audit record.
Related reading
GitHub Copilot Impact Dashboard Adds an ROI View
On August 7, 2026, GitHub added a Potential return on investment section to the Copilot impact dashboard. The view compares adoption phases and shows average cost per developer, pull-request output, and merge-rate signals. It is useful for asking whether spending and workflow adoption deserve a closer review, but it is not a financial audit or proof that Copilot caused a business result. A defensible first review fixes the organization and time window, reconciles AI-credit usage and active developers, samples pull-request quality and rework, and separates tool metrics from delivery and business outcomes. Teams should avoid ranking individuals on one number or expanding budgets before the measurement definition is stable.
GitHub Copilot Code Review Adds Lite and Balanced Effort Levels
GitHub announced on August 7, 2026 that Lite and Balanced effort levels for Copilot code review are generally available, replacing the former Low and Medium choices. A reviewer can select a level for an individual review, while organizations can set a default. The useful task is not to assume that deeper analysis is always better: test Lite on small, reversible changes and Balanced on complex or sensitive changes, then record findings, false positives, latency, AI-credit use, and the human decision. Availability still depends on client version, plan, and organization policy, so verify the control before documenting it as a team standard.
AWS Shows AgentCore Policy Workflows with Tenant Isolation and Versioned Skills
AWS’s August 7, 2026 machine-learning case study describes how Cohere Health uses Amazon Bedrock AgentCore to turn clinical prior-authorization policies into structured data. The architecture combines Runtime microVM isolation, Gateway for unified tool access, Memory for session history, and the Agent Skills open standard for versioned domain capabilities. Skills are evaluated with reference data and expert review before release. The reusable lesson is not to automate medical judgment with one prompt. It is to separate tenants, tools, data sources, versions, feedback, and approval, then begin with public or de-identified documents before connecting sensitive business data. Keep the same evidence trail when the workflow changes.
GitHub Copilot Weekly Releases Add Sessions, Worktrees, and Rewind
GitHub’s August 7, 2026 Copilot roundup covers the desktop app, CLI, and VS Code. Users can see which model handled a completed request, manage concurrent sessions, create an isolated worktree for experiments, and use rewind to restore Copilot changes even in a directory without Git. The practical value is controlled experimentation rather than faster generation alone. Start with a small repository that contains no secrets or customer data, record the model, prompts, commands, file changes, tests, and credit usage, and keep a human approval step before applying the workflow to production code. This creates evidence for cost and quality decisions instead of relying on impressions.
Kimi K3 Reaches GitHub Copilot: Check Plan Access, Model Policy, and Usage Billing
GitHub announced on August 6, 2026 that Kimi K3 is gradually rolling out to Copilot Pro, Pro+, Max, Business, and Enterprise plans. Eligible users can select it in places such as Visual Studio Code, Copilot CLI, GitHub, and supported IDEs, but availability depends on plan, client, and rollout status. GitHub says Kimi K3 uses provider list pricing under usage-based billing. Business and Enterprise administrators must enable the Kimi K3 policy before members can use it and should review open-weight model governance. For ordinary users, the practical first step is a bounded non-production test with a recorded budget, permissions, changes, tests, and human review rather than an immediate production rollout.
GitHub's VS Code July Update Adds an Agents Window for Claude, Codex, and Copilot
GitHub summarized the July 2026 Copilot releases for Visual Studio Code on July 30, 2026. The public-preview Agents window brings local, background, and cloud sessions into one view, while the Agent Host can run coding harnesses such as Claude Code, OpenAI Codex CLI, and GitHub Copilot CLI. VS Code 1.131 also adds multi-chat support and worktree isolation for any harness, with clearer session status and subagent structure. For users, the practical opportunity is parallel task management without mixing branches or context. Adoption checks should cover permissions, repository scope, worktree cleanup, cost limits, logs, tests, and human review before real code is merged.
Summary
GitHub's new agent-app metrics give teams a sharper cost and permission view. Start with stable IDs and separate windows, then add governance only after a read-only audit is trusted.
