GitHub Copilot 使用指标 API 新增自定义技能、Agent 与 MCP 服务器具名统计

Copilot 使用情况指标（usage metrics）现已支持显示组织创建的技能（skills）、自定义 Agent、模型上下文协议（Model Context Protocol, MCP）服务器、斜杠命令（slash commands）以及插件的具体配置名称，而不再统一归入 other 或 custom。此更新建立在 9 月发布的 Agentic CLI 定制化指标 基础之上。

• 显示具体名称（Named entries）： 在企业与组织报告中（包括单用户 1 天和 28 天报告、聚合 1 天报告以及聚合 28 天报告中的 day_totals），totals_by_skill、totals_by_custom_agent、totals_by_mcp、totals_by_slash_cmd 和 totals_by_plugin 数组现在会显示客户定义项目的配置名称，而非 other 或 custom。
• 展示更多条目（More entries）： 每个 totals_by_* 列表单条记录最多可包含 25 个条目（此前为 5 个），以便管理者全面掌握开发者使用的各类长尾定制工具。其余超出上限的活跃数据将合并到末尾的 other 条目中。
• 计数规则保持不变（Unchanged counts）： interaction_count 以及 distinct_*_use_count 字段的统计计算方式与此前完全一致。

对企业组织而言，最具价值的定制化扩展往往出自其内部团队。现在，管理员可以清晰洞察开发者实际使用了哪些内部技能、自定义 Agent 和 MCP 服务器，在新工具发布后持续追踪采纳率，并在最需要的地方开展针对性赋能。

• 覆盖范围（Coverage）： 名称数据由 Copilot CLI（交互式会话与 Prompt 模式）、GitHub Copilot 应用、Agent Client Protocol (ACP) 集成（如 JetBrains）以及 Copilot SDK 统一上报。Prompt 模式、独立应用及 ACP 集成需要 Copilot CLI 1.0.97 或更高版本；Copilot SDK 需要 v1.0.21 或更高版本；IDE 仅在 Agent 体验运行于 Copilot SDK v1.0.21 或更高版本时上报名称，IDE 内置的 Chat 遥测数据不会上报名称。
• 配置名称处理（Configured names）： 名称按实际配置原样上报，会进行首尾空格修剪并限制在 128 个字符以内。形似文件路径的名称将继续归类至 other 或 custom。在向组织外部共享报告之前，请注意审核相关名称。
• 准确性说明（Accuracy）： 这些指标来源于客户端遥测数据，在客户端版本过旧或遥测被拦截时可能会出现统计不足的情况。建议将其用于评估趋势与采纳度，而非作为精确审计结算的依据。
• 历史数据（History）： 具名统计自本版本发布后处理的报告日起生效，更早的历史周期仍将显示为 other 或 custom。
• 访问权限（Access）： 企业所有者（enterprise owners）、账单管理员（billing managers）、组织所有者（organization owners），以及任何拥有“View Copilot Metrics”权限的自定义组织/企业角色均可访问报告。同时必须启用 Copilot 使用指标策略（usage metrics policy）。

欢迎查阅 Copilot 使用情况指标 API 文档 开始使用。

Copilot usage metrics now show the names of the skills, custom agents, Model Context Protocol (MCP) servers, slash commands, and plugins that your organization creates, instead of grouping them under other or custom. This builds on the agentic CLI customization metrics released in September.

• Named entries: In enterprise and organization reports, including per-user 1-day and 28-day reports, aggregated 1-day reports, and day_totals in aggregated 28-day reports, the totals_by_skill, totals_by_custom_agent, totals_by_mcp, totals_by_slash_cmd, and totals_by_plugin arrays now show the configured name of a customer-defined item instead of other or custom.
• More entries: Each totals_by_* list now includes up to 25 entries per record, up from five, so you can see more of the long tail of customizations your developers use. Any remaining activity is combined into a trailing other entry.
• Unchanged counts: interaction_count and the distinct_*_use_count fields are calculated the same way as before.

The customizations that matter most to an organization are often the ones its own teams build. Administrators can now see which internal skills, custom agents, and MCP servers developers actually use, track adoption after rolling out a new one, and focus enablement where it is needed.

• Coverage: Names are reported from Copilot CLI (interactive sessions and prompt mode), the GitHub Copilot app, Agent Client Protocol (ACP) integrations such as JetBrains, and the Copilot SDK. Prompt mode, the app, and ACP integrations require Copilot CLI 1.0.97 or later. The Copilot SDK requires v1.0.21 or later. IDEs report names when their agent experiences run on the Copilot SDK v1.0.21 or later. Names aren’t reported from an IDE’s built-in chat telemetry.
• Configured names: Names are reported as they are configured, trimmed and limited to 128 characters. Names that look like file paths stay grouped under other or custom. Review names before sharing reports outside your organization.
• Accuracy: These metrics come from client telemetry and can undercount activity, for example when clients are outdated or telemetry is blocked. Use them to understand trends and adoption rather than for exact accounting.
• History: Names appear starting with report days processed after this release. Earlier days still show other or custom.
• Access: Reports are available to enterprise owners and billing managers, organization owners, and anyone with a custom organization or enterprise role that grants the “View Copilot Metrics” permission. The Copilot usage metrics policy must be enabled.

Visit the Copilot usage metrics API documentation to get started.