GitHub Copilot Usage Reports Add Per-Model Token Detail Behind AI Credits
The August 11 report now exposes input, output, cache-read, and cache-write tokens, but cost attribution still needs task and quality evidence.
Key takeaways
GitHub added a per-model token breakdown to AI usage reports on August 11, 2026. For each model, users can now see input, output, cache-read, and cache-write tokens beside the AI Credits consumed. The detail is available to Copilot Business and Enterprise administrators and to individual Copilot users through a downloadable report on the AI usage page in billing settings. It can reveal whether long context, verbose output, cache behavior, or retries explain a charge. However, token detail explains consumption rather than quality or return on investment. Use a fixed billing window and task labels, then compare failures, rework, accepted output, and human review alongside tokens and credits before changing a model, prompt, or workflow policy.
# GitHub Copilot Usage Reports Add Per-Model Token Detail Behind AI Credits
August 13, 2026
Direct answer
Download the AI usage report, aggregate every token type and AI Credits by model, and compare them within one task and time window. Keep quality, failures, rework, and human acceptance beside the cost data.
Fact sources
GitHub announced per-model input, output, cache-read, and cache-write token detail on August 11, 2026.
The new fields sit beside AI Credits, exposing the usage components behind a charge that previously lacked token detail.
Copilot Business and Enterprise administrators and individual Copilot users can obtain the breakdown from a downloaded billing report.
Five steps to investigate AI cost with token detail
- Download a report for one billing cycle using a fixed time zone.
- Aggregate input, output, cache-read, cache-write tokens, and AI Credits by model.
- Label major work by repository, task, user, and successful or failed outcome.
- Inspect long inputs, repeated context, verbose output, cache misses, and retries.
- Retest after a model or prompt change and compare quality, rework, and human acceptance too.
Why it matters
AI Credits show the billing result, while token detail gives a closer view of causes. Without task and outcome data, high use can be mislabeled as waste and low use as efficiency.
Impact for ordinary AI users
Individuals can explain charges more precisely, and administrators can locate model-level cost. They also need policies for report access, user data, time zones, and retention.
Related tools and tutorials
Start with one reversible task, verify version, permissions, cost, and logs, then record the result in the team runbook.
AI software and tools · AI account and cost services · AI skill tutorials · AI frontier news
FAQ
Where is the token breakdown?
GitHub says it is in the downloadable AI usage report from billing settings, not only in the on-screen total.
Are more cache-read tokens always better?
No. Interpret cache behavior with price, latency, task success, and output quality.
Is the model with fewer tokens automatically cheaper overall?
Not if it creates more failures, retries, rework, or human correction.
Source links
- GitHub Changelog: Per-model token breakdown (2026-08-11)
- GitHub Docs: Billing reports reference
- GitHub Docs: Models and pricing for Copilot
What this means for everyday users
Record billing window, time zone, model, token type, AI Credits, task, failure, rework, acceptance, and report access.
Related reading
From Chat Boxes to Personal AI Companions: AI Assistants Are Entering the Desktop Execution Era
AI assistants are moving from answering questions toward continuing real tasks. AI agents, MCP tool ecosystems, personal memory, and local workbenches are pushing this shift together. For users, the real value is not another chat box, but less repeated context setup and more continuity from thinking to doing.
Copilot in Visual Studio Adds PR Exploration, a BYOM Migration, and NuGet Fixes
GitHub summarized three September updates for Copilot in Visual Studio 2026 on October 22, 2026. The Git agent can explore an attached pull request and link back to comments and files. Bring Your Own Model remains in preview but now requires the new Agent experience, and previously configured Ollama models must be added again. NuGet Audit warnings can open Copilot Chat with the NuGet MCP server to propose dependency fixes. This article gives .NET developers a cautious upgrade checklist: preserve current settings, validate each feature independently, review package and lock-file changes, run targeted tests and vulnerability scans, and keep a rollback path. Summaries and suggested fixes remain review inputs, not verified outcomes.
Bayer Shares Production Lessons From 22 Specialist Agents: HTTP Success Is Not Task Success
AWS published Bayer Crop Science’s Agentic Decision Engine case study on October 23, 2026. The production system runs 22 specialist agents over governed analytics workflows, models, logs, and visualization tools. This article turns the architecture into five reusable acceptance checks for enterprise agent teams: persist the state needed to resume work, define identity and authorization at every boundary, scope each agent’s tool catalog, distinguish transport success from task success, and release to a gated group before broader access. It also explains why Bayer’s adoption and resolution figures are evidence about one implementation, not promises for another organization. The focus is operational proof, least privilege, rollback, and observable outcomes rather than prompt polish.
GitHub Copilot in Teams Turns Notifications Into Pull Requests: What to Check Before Review
GitHub updated its Microsoft Teams app on October 23, 2026, so an issue notification in a channel, group chat, or private chat can become a Copilot task that investigates the problem, proposes a fix, and opens a pull request. This article helps development and product teams adopt the workflow without mistaking an automated pull request for shipped code. It explains the consolidated app, repository connection, the November 16 retirement of the legacy GitHub app, and the review boundary. A practical acceptance checklist asks teams to reproduce the issue, inspect changed files, run targeted tests, verify permissions, and keep merge and deployment as explicit human decisions.
IskayPet Connects SharePoint to a Managed Knowledge Base: Validate Permissions Before Answers
AWS published IskayPet’s corporate knowledge assistant case study on October 22, 2026. The system connects Amazon Bedrock Managed Knowledge Bases to existing SharePoint repositories and answers cited questions across retail operations, veterinary care, onboarding, and procurement in four languages and three countries. This article turns the case into a practical acceptance plan for knowledge owners. It checks source scope, inherited permissions, hybrid retrieval, duplicate and fragment removal, citation quality, feedback, and token cost before expansion. It also separates the customer’s reported production results from what another organization should expect. A managed retrieval stack reduces infrastructure work, but it does not remove content ownership, access reviews, evaluation datasets, or human verification of important answers.
GitHub Copilot Metrics Add OpenCode and Other Clients: Requests Are Not Prompts
GitHub added totals_by_client to the Copilot usage metrics API on October 23, 2026. Enterprise and organization reports can now show model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, GitHub apps, cloud agents, code review, VS Code, JetBrains, and other clients. This article helps administrators build reliable one-day and 28-day reports without confusing model calls with user prompts. It explains request, session, token, model, and selection-mode fields; separates client traffic from agent-app jobs; and adds checks for unknown identifiers, empty arrays, permissions, and coverage. The result is a governance trend report, not an exact invoice or individual productivity score.
Summary
Per-model token detail makes AI Credits explainable, not automatically efficient. Join billing, task, quality, and human-cost evidence before changing model policy.