AI Devtools Radar

GitHub Copilot

代码助手github.com13 条已发布变化

2 个来源在监控

变化时间线

deprecationhigh

多个 GitHub Copilot 模型将于 2026 年 10 月 2 日停用

依赖 Gemini 3.5 Flash、Gemini 3.6 Flash、Kimi K2.7 Code 或 Claude Opus 4.7 的用户必须在 2026 年 10 月 2 日前迁移到建议的替代方案。管理员需要在 Copilot 设置中启用替代模型。

证据
+We will deprecate the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions) on October 2nd, 2026: Model | Deprecation date | Suggested alternative Gemini 3.5 Flash | 2026-10-02 | Gemini 3.8 Flash Gemini 3.6 Flash | 2026-10-02 | Gemini 3.8 Flash Kimi K2.7 Code | 2026-10-02 | Kimi K3 Claude Opus 4.7 | 2026-10-02 | Claude Opus 5

github.blog

feature

企业管理设置现在支持为 Copilot 对话配置默认模型

企业管理员现在可以全局或按团队设置首选默认模型，团队可在配置允许的情况下覆盖默认值。这为跨企业管理 Copilot 部署提供了更多灵活性。

证据
+You can now set your preferred GitHub Copilot model as the default for new conversations through enterprise-managed settings. This lets you choose the default model that best fits your workflows.

github.blog · 另有 1 个来源报告了同一变化

pricinghigh

GitHub Copilot 个人版定价页改为四档：Free、Pro、Pro+ 和 Max

四档价格分别为 0、10、39 和 100 美元每月；把任务委托给 Claude、Codex 等第三方 coding agent 的能力划在 Pro+ 和 Max 档。

证据
+Free For getting started with GitHub Copilot. $0USD Pro For everyday coding with agents in GitHub Copilot. $10USDper user / month Pro+ For more complex development with premium models. $39USDper user / month Max For sustained, high-volume agent workflows with GitHub Copilot. $100USDper user / month

github.com

featurehigh

GitHub Copilot for JetBrains 现支持企业托管设置，用于插件治理、MCP servers、OpenTelemetry 和权限管理

企业管理员现在可以集中管理和控制 Copilot 插件治理、MCP server 访问、遥测收集和权限模式，覆盖整个组织的所有 JetBrains IDE 用户。

证据
+GitHub Copilot for JetBrains now supports enterprise managed settings for plugin governance, MCP server access, OpenTelemetry, and permission modes. Administrators can now apply consistent controls for everyone on your enterprise's Copilot plan.

github.blog

featurehigh

Copilot 记忆功能现已在 GitHub Copilot for JetBrains 中推出，用于在聊天会话间保留上下文

用户可以在对话间维持上下文，无需重复提供相同的项目详情或偏好设置。通过 Copilot 设置门户中的切换按钮进行管理。

证据
+Copilot memory can now retain and recall useful information across agent chat sessions. This helps you maintain context between conversations instead of repeatedly providing the same project details or preferences.

github.blog

api

Copilot 使用指标 API 现在报告代理应用活动

企业和组织管理员现在可以通过 Copilot 使用指标 API 在企业、组织、企业用户和组织用户报告中跟踪各个代理应用 (如 Claude 和 Codex 代理) 的使用情况。

证据
+The Copilot usage metrics API now reports that activity, broken out by individual agent. The usage metrics API does this in the enterprise, organization, enterprise-user, and organization-user 1-day and 28-day reports.

github.blog

pricinghigh

Kimi K3 定价公布：输入 token 每 100 万个 $3、输出 token 每 100 万个 $15、缓存输入 token 每 100 万个 $0.30

用户将按使用量计费购买 Kimi K3 模型，输入、输出和缓存输入 token 的费率不同。由于 GitHub Actions 事故，定价文档发布暂时暂停。

证据
+Kimi K3 pricing, which will be $3 per 1M input tokens, $15 per 1M output tokens, and $0.30 per 1M cached input tokens.

github.blog

feature

Copilot cloud agent 现已支持为兼容模型自定义推理级别

付费 Copilot 计划用户（Pro、Pro+、Business、Enterprise、Max）在委托任务时现在可以控制模型推理深度，以权衡答案质量和 token/积分消耗。

证据
+When you delegate a task to GitHub Copilot cloud agent, you can now set the reasoning level for models that support it. This allows you to control how much the model reasons before it responds.

github.blog

deprecationhigh

Gemini 2.5 Pro 和 Gemini 3 Flash 模型在 GitHub Copilot 中已弃用

用户必须从 Gemini 2.5 Pro 迁移到 Gemini 3.1 Pro (Preview)，从 Gemini 3 Flash 迁移到 Gemini 3.6 Flash。Copilot Enterprise 管理员需要通过策略设置启用替代模型。弃用的模型在 Copilot Chat、内联编辑、ask/agent 模式和代码补全中不再可用。

证据
+As of today, July 31, 2026, we have deprecated the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions). Gemini 2.5 Pro 2026-07-31 Gemini 3.1 Pro (Preview) Gemini 3 Flash 2026-07-31 Gemini 3.6 Flash

github.blog · 另有 1 个来源报告了同一变化

pricing

Grok 4.5 按使用量计费，定价为供应商列表价格

Copilot 用户将按照 GitHub Copilot 按使用量计费模式，按 xAI 供应商列表价格费率对 Grok 4.5 使用进行收费。

证据
+This model is billed at provider list pricing under usage-based billing.

github.blog

featurehigh

GitHub Copilot app 现拥有独立于 Copilot CLI 的专用访问策略

企业和组织管理员现在可以通过专用策略独立控制对 Copilot app 的访问，有三个选项：在所有地方启用、在所有地方禁用或让组织决定。可以更精细地控制团队可以使用哪些 Copilot 客户端。

证据
+The GitHub Copilot app now has its own policy, so you can control who has access to it at the enterprise and organization levels. Until now, access to the Copilot app depended on your GitHub Copilot CLI policy being enabled. From several conversations with customers, we understand that many of you want to manage each client independently. Now the Copilot app and the Copilot CLI each have their own policy, giving you the flexibility and control to enable the right clients for your teams.

github.blog

feature

Copilot 代码审查新增防火墙、自定义设置步骤和独立运行器配置

用户现在可以使用防火墙设置、自定义设置步骤和独立运行器配置来自定义 Copilot 代码审查，以增强安全性和灵活性。

证据
+Copilot code review now utilizes a firewall, custom setup steps, and independent runner configurations.

github.blog

apihigh

Copilot 新增仓库级用量指标 API 端点

企业和组织管理员现在可以通过两个新的 REST API 端点访问每个仓库的 Copilot 编码代理和代码审查拉取请求活动的细分数据。

证据
+Two new endpoints return a per-repository report for a single day: <ul> <li><code>GET /enterprises/{enterprise}/copilot/metrics/reports/repos-1-day?day=YYYY-MM-DD</code></li> <li><code>GET /orgs/{org}/copilot/metrics/reports/repos-1-day?day=YYYY-MM-DD</code></li> </ul> Each response returns the following activity: <ul> <li>Pull requests created and merged by Copilot coding agent.</li> <li>Pull requests reviewed by Copilot code review, with suggestion counts broken down by comment type.</li> </ul>

github.blog