GitHub Copilot 政策与计费变更：9月1日起重新开放注册，10月1日起预付费
Upcoming changes to GitHub Copilot policies and billing
Copilot 用户注意：10 月 1 日起席位预付费，9 月 28 日前需确认统一体验政策与代码审查默认级别，否则将自动切换。建议管理员在截止日期前调整设置。
To provide a strong, consistent Copilot experience, we’re making three separate, upcoming changes to Copilot policies and billing. Please review the upcoming updates to understand what may impact you.
为了提供强大且一致的 Copilot 体验，我们即将对 Copilot 政策和计费进行三项独立更改。请查看即将到来的更新，以了解可能对您产生的影响。
Reopening Copilot Business and Enterprise signups with billing updates
重新开放 Copilot Business 和 Enterprise 注册，并更新计费方式
Starting September 1, 2026, GitHub will start reenabling sign-ups for new Copilot Business and Copilot Enterprise customers paying by credit card or PayPal. To improve availability and reliability of Copilot services, we’re strengthening account vetting and updating billing experiences for customers who pay by credit card or PayPal.
从 2026 年 9 月 1 日起，GitHub 将重新启用通过信用卡或 PayPal 支付的新 Copilot Business 和 Copilot Enterprise 客户的注册。为了提高 Copilot 服务的可用性和可靠性，我们正在加强账户审核，并更新通过信用卡或 PayPal 支付的客户的计费体验。
What’s changing
变更内容
- All new Copilot Business or Copilot Enterprise seat assignments will require payment for each seat before users gain Copilot access.
- At the start of the next billing cycle, all Copilot Business and Copilot Enterprise seats assigned will incur an upfront charge. This includes existing customers starting October 1, 2026.
- If you exceed your included usage, additional payment may be required for you and your users to continue using Copilot.
- Included usage may be prorated across the month to align with the seat cost proration.
- 所有新的 Copilot Business 或 Copilot Enterprise 席位分配将要求在每个用户获得 Copilot 访问权限之前支付每个席位的费用。
- 在下一个计费周期开始时，所有分配的 Copilot Business 和 Copilot Enterprise 席位将产生预付费。这包括从 2026 年 10 月 1 日起的现有客户。
- 如果您超出包含的使用量，您和您的用户可能需要支付额外费用才能继续使用 Copilot。
- 包含的使用量可能会按月按比例分配，以与席位成本按比例分配保持一致。
What’s not changing
不变的内容
- Copilot Business and Copilot Enterprise prices are not changing.
- Revoking a seat does not result in a prorated refund. The removal will be reflected in your next monthly billing cycle.
- All seats added in the middle of a billing cycle will continue to be prorated from date of assignment to end of bill cycle.
- Additional usage exceeding included allowances will remain available for purchase.
- Spend controls, usage tracking, and the option to purchase additional AI credits will remain available.
- Copilot Business 和 Copilot Enterprise 的价格不变。
- 撤销席位不会产生按比例退款。移除将在您的下一个月度计费周期中反映。
- 在计费周期中间添加的所有席位将继续从分配日期到计费周期结束按比例计算。
- 超出包含限额的额外使用量仍可购买。
- 支出控制、使用跟踪以及购买额外 AI 额度的选项仍将可用。
Existing Copilot Business and Copilot Enterprise customers can expect these billing updates to take effect starting October 1, 2026.
现有的 Copilot Business 和 Copilot Enterprise 客户可以预期这些计费更新将从 2026 年 10 月 1 日起生效。
Fully canceling Copilot and returning later may trigger updated account vetting and billing behaviors.
完全取消 Copilot 并在稍后返回可能会触发更新的账户审核和计费行为。
For more information, read our Copilot Quick Start documentation.
有关更多信息，请阅读我们的 Copilot 快速入门文档。
Copilot cloud agent, Copilot Chat on github.com, and Copilot Chat in GitHub Mobile are converging to a single experience and policy
Copilot 云代理、github.com 上的 Copilot Chat 和 GitHub Mobile 中的 Copilot Chat 将合并为单一体验和政策
No earlier than September 28th, 2026, GitHub will relaunch Copilot Chat on github.com, Copilot Chat in GitHub Mobile, and GitHub Copilot cloud agent as a single, unified Copilot experience.
不早于 2026 年 9 月 28 日，GitHub 将把 github.com 上的 Copilot Chat、GitHub Mobile 中的 Copilot Chat 和 GitHub Copilot 云代理重新推出为统一的 Copilot 体验。
What’s changing
变更内容
- The separate policies for these experiences will be replaced by a single policy.
- This unified Copilot experience will be enabled by default after launch.
- Cloud agent will leverage Sandbox to provide a faster cloud experience.
- Copilot on github.com will fully migrate to the agent sessions experience, previously used only by Copilot cloud agent. As a result, chat data will be retained for the life of the account instead of 28 days, aligning with our existing Copilot cloud agent experience.
- 这些体验的单独政策将被单一政策取代。
- 这种统一的 Copilot 体验将在发布后默认启用。
- 云代理将利用沙盒提供更快速的云体验。
- github.com 上的 Copilot 将完全迁移到代理会话体验，此前仅由 Copilot 云代理使用。因此，聊天数据将保留至账户生命周期，而非 28 天，这与我们现有的 Copilot 云代理体验保持一致。
Stay opted in
保持启用状态
No changes are required to keep Copilot available on github.com and GitHub Mobile. However, if you opt out of the unified experience, you or your teams will lose access to Copilot on github.com and GitHub Mobile after the new experience launches.
无需进行任何更改即可在 github.com 和 GitHub Mobile 上继续使用 Copilot。但是，如果您选择退出统一体验，您或您的团队将在新体验推出后失去对 github.com 和 GitHub Mobile 上 Copilot 的访问权限。
Business and enterprise administrators should review the policy before September 28th, 2026 and confirm that it reflects how they want to manage Copilot access for their teams.
企业和组织管理员应在 2026 年 9 月 28 日之前审查该策略，并确认其反映了他们希望如何管理团队对 Copilot 的访问权限。
To update the policy:
要更新策略：
- Go to Copilot settings on github.com.
- Select Copilot cloud agent (coming soon).
- Set the policy option.
- 转到 github.com 上的 Copilot 设置。
- 选择 Copilot 云代理（即将推出）。
- 设置策略选项。
Copilot code review default is changing to Balanced effort level
Copilot 代码审查默认级别更改为平衡努力级别
Following the release of Copilot code review effort levels, the default review effort level for GitHub Copilot code review is changing from Lite to Balanced.
在 Copilot 代码审查努力级别发布后，GitHub Copilot 代码审查的默认审查努力级别将从 Lite 更改为 Balanced。
How review effort level defaults work
审查努力级别默认值的工作原理
You can set a default review effort level at the organization and repository levels:
您可以在组织和仓库级别设置默认审查努力级别：
- The organization default applies to all repositories owned by the organization that haven’t selected their own review effort level.
- The repository default applies to all automatically requested reviews within the repository. For manually requested reviews, you can select which effort level is used from the “Reviewers” bar in the pull request.
- 组织默认值适用于该组织拥有的所有未选择自己审查努力级别的仓库。
- 仓库默认值适用于仓库内所有自动请求的审查。对于手动请求的审查，您可以从拉取请求中的“审查者”栏中选择使用的努力级别。
Balanced is becoming the default effort level
Balanced 成为默认努力级别
For existing and new repositories and organizations using Copilot code review, the review effort value of Default uses Balanced starting September 28th, 2026.
对于使用 Copilot 代码审查的现有和新建仓库及组织，从 2026 年 9 月 28 日起，默认的审查努力值将使用 Balanced。
If you’d prefer to keep Lite as your default experience, change your review effort level away from Default and explicitly select Lite in your repository or organization settings before September 28th, 2026. We’ll respect that selection and won’t switch your default to Balanced.
如果您希望保持 Lite 作为默认体验，请在 2026 年 9 月 28 日之前将您的审查努力级别从 Default 更改为明确选择 Lite，在您的仓库或组织设置中进行。我们将尊重该选择，并且不会将您的默认级别切换为 Balanced。
Review the Copilot code review documentation to understand how this may affect your usage.
请查阅 Copilot 代码审查文档，了解这可能如何影响您的使用。
The post Upcoming changes to GitHub Copilot policies and billing appeared first on The GitHub Blog.
文章《GitHub Copilot 策略和计费的即将更改》最初出现在 GitHub 博客上。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力