GitHub Copilot: Usage metrics API now distinguishes BYOK and custom enterprise models
GitHub has expanded the Copilot usage metrics API with separate tracking of BYOK (custom keys/local models) and custom enterprise models, so they are not merged with Copilot's hosted models.
GitHub has expanded the Copilot usage metrics API with new fields for tracking BYOK (bring your own key) and custom enterprise models. According to the company, until now the usage of BYOK and custom models had been mixed into the overall figures for Copilot's hosted models, because local and custom models often carry the same names as Copilot models.
The new data distinguishes two types of BYOK: the used_local_byok field shows at the user level whether that user made at least one request via local BYOK in Copilot CLI or the Copilot app on a given day. The totals_by_local_byok field contains counts of sessions, requests, prompts, and tokens broken down by byok_kind (local_managed, local_user, local_auto, remote_user) and by surface (copilot_cli or copilot_app). Aggregated reports additionally contain daily, weekly, and monthly active user counts for local BYOK. Local BYOK includes a custom provider key and local models served by tools such as Ollama, Foundry Local, LM Studio, or llama-server.
For custom enterprise models, GitHub added a boolean field is_custom_enterprise_model to each entry in totals_by_client[].totals_by_model[]. A value of true means that the request used a custom model configured for the given enterprise or organization; GitHub tracks this data server-side, so the field applies to all clients, including IDEs.
All the new reports are available in reports at both the enterprise and organization level, at the individual user level as well as aggregated, in both 1-day and 28-day windows. The existing overall counts (totals_by_cli, totals_by_copilot_app) remain unchanged. According to GitHub, local BYOK usage still remains undifferentiated by specific model name (it is reported as unknown). Access to the data requires the View Copilot Metrics permission and the Copilot usage metrics policy to be enabled.
Why it matters
For companies and administrators, this is a direct governance and cost-control tool — until now, the usage of local models (BYOK) and custom enterprise models had been mixed together with GitHub's hosted models, which complicated tracking actual tool adoption and costs. Separate metrics will make it possible to find out how many users use custom keys or local models instead of hosted ones, and to better plan licenses and security policies. For individual developers, the change itself does not alter any Copilot functionality — it is purely administrative-side reporting.
Relevant practical impact
What this means
For a business
GitHub Copilot administrators can now see separate reports in the usage metrics API for BYOK (local models via Ollama, Foundry Local, LM Studio, llama-server) and for custom enterprise models, enabling more precise tracking of who uses Copilot and how, separately from GitHub's hosted models.
Risks and complianceCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.