今天凌晨copilot把 Claude opus4.6关了，新用户暂停注册pro和pro+
- 内容介绍
- 文章标签
- 相关推荐
image537×926 30.5 KB
image2198×800 191 KB
本文由 简悦 SimpRead 转码， 原文地址 github.blog
We’re making these changes to ensure a reliable and predictable experience for existing customers.
1200×630 61.4 KB
Today we’re making the following changes to GitHub Copilot’s Individual plans to protect the experience for existing customers: pausing new sign-ups, tightening usage limits, and adjusting model availability. We know these changes are disruptive, and we want to be clear about why we’re making them and how they will affect you.
今天，我们正在对 GitHub Copilot 的个人计划进行以下变更，以保护现有客户的体验：暂停新注册、收紧使用限制和调整模型可用性。我们知道这些变更具有破坏性，我们希望清楚地说明我们为什么要做这些变更，以及它们将如何影响您。
Agentic workflows have fundamentally changed Copilot’s compute demands. Long-running, parallelized sessions now regularly consume far more resources than the original plan structure was built to support. As Copilot’s agentic capabilities have expanded rapidly, agents are doing more work, and more customers are hitting usage limits designed to maintain service reliability. Without further action, service quality degrades for everyone.
代理工作流从根本上改变了 Copilot 的计算需求。长时间运行的并行会话现在经常消耗的资源远远超过最初计划结构所支持的。随着 Copilot 的代理能力快速扩展，代理正在做更多工作，更多客户正在达到为维持服务可靠性而设计的使用限制。如果不采取进一步行动，每个人的服务质量都会下降。
We’ve heard your frustrations about usage limits and model availability, and we need to do a better job communicating the guardrails we are adding—here’s what’s changing and why.
我们听说了您对使用限制和模型可用性的不满，我们需要更好地传达我们正在添加的护栏------以下是变化的内容和原因。
- New sign-ups for GitHub Copilot Pro, Pro+, and Student plans are paused. Pausing sign-ups allows us to serve existing customers more effectively.
GitHub Copilot Pro、Pro+ 和 Student 计划的新注册将被暂停。暂停注册使我们能够更有效地为现有客户服务。 - We are tightening usage limits for individual plans. Pro+ plans offer more than 5X the limits of Pro. Users on the Pro plan who need higher limits can upgrade to Pro+. Usage limits are now displayed in VS Code and Copilot CLI to make it easier for you to avoid hitting these limits.
我们正在收紧各个计划的使用限制。Pro+ 计划提供的限制超过 Pro 的 5 倍。需要更高限制的 Pro 计划用户可以升级到 Pro+。使用限制现在显示在 VS Code 和 Copilot CLI 中，以便您更容易避免达到这些限制。 - Opus models are no longer available in Pro plans. Opus 4.7 remains available in Pro+ plans. As we announced in our changelog, Opus 4.5 and Opus 4.6 will be removed from Pro+.
作品模型在 Pro 计划中不再可用。作品 4.7 在 Pro+ 计划中仍然可用。正如我们在变更日志中所宣布的，作品 4.5 和作品 4.6 将从 Pro+ 计划中移除。
These changes are necessary to ensure we can serve existing customers with a predictable experience. If you hit unexpected limits or these changes just don’t work for you, you can cancel your Pro or Pro+ subscription and you will not be charged for April usage. Please reach out to GitHub support between April 20 and May 20 for a refund.
这些变更是必要的，以确保我们能够以可预测的体验为现有客户提供服务。如果您达到了意想不到的限制，或者这些变更不适合您，您可以取消 Pro 或 Pro+ 订阅，并且不会收取四月份使用费。请在 4 月 20 日至 5 月 20 日期间联系 GitHub 支持部门申请退款。
How usage limits work in GitHub Copilot
使用限制如何在 GitHub 副驾驶中工作
GitHub Copilot has two usage limits today: session and weekly (7 day) limits. Both limits depend on two distinct factors—token consumption and the model’s multiplier.
GitHub Copilot 目前有两个使用限制：会话限制和每周 (7 天) 限制。这两个限制都取决于两个不同的因素------代币消耗和模型的乘数。
The session limits exist primarily to ensure that the service is not overloaded during periods of peak usage. They’re set so most users shouldn’t be impacted. Over time, these limits will be adjusted to balance reliability and demand. If you do encounter a session limit, you must wait until the usage window resets to resume using Copilot.
会话限制主要是为了确保服务在峰值使用期间不会过载。它们的设置是为了使大多数用户不会受到影响。随着时间的推移，这些限制将被调整，以平衡可靠性和需求。如果你确实遇到了会话限制，你必须等到使用窗口重置后才能恢复使用 Copilot。
Weekly limits represent a cap on the total number of tokens a user can consume during the week. We introduced weekly limits recently to control for parallelized, long-trajectory requests that often run for extended periods of time and result in prohibitively high costs.
每周限制代表了用户在一周内可以使用的代币总数的上限。我们最近引入了每周限制，以控制并行的、长时间运行的请求，这些请求通常需要长时间运行，并导致令人望而却步的高成本。
The weekly limits for each plan are also set so that most users will not be impacted. If you hit a weekly limit and have premium requests remaining, you can continue to use Copilot with Auto model selection. Model choice will be reenabled when the weekly period resets. If you are a Pro user, you can upgrade to Pro+ to increase your weekly limits. Pro+ includes over 5X the limits of Pro.
每个计划的每周限额也被设置，以确保大多数用户不会受到影响。如果您达到了每周限额，但仍有高级请求，您可以继续使用 Copilot 并进行自动型号选择。当每周期限重置时，型号选择将重新启用。如果您是 Pro 用户，您可以升级到 Pro+ 以增加您的每周限额。Pro+ 包含超过 5 倍的 Pro 限额。
Usage limits are separate from your premium request entitlements. Premium requests determine which models you can access and how many requests you can make. Usage limits, by contrast, are token-based guardrails that cap how many tokens you can consume within a given time window. You can have premium requests remaining and still hit a usage limit.
使用限制与您的高级请求权限是分开的。高级请求决定了您可以访问哪些型号以及可以发出多少请求。相比之下，使用限制是基于令牌的防护措施，它限制了您在给定时间窗口内可以使用的令牌数量。您可以保留高级请求，但仍然达到使用限制。
Avoiding surprise limits and improving our transparency
避免意外限制并提高我们的透明度
Starting today, VS Code and Copilot CLI both display your available usage when you’re approaching a limit. These changes are meant to help you avoid a surprise limit.
从今天开始，VS Code 和 Copilot CLI 都会在您接近限制时显示您的可用性。这些更改旨在帮助您避免意外的限制。
1394×1222 66.9 KBUsage limits in VS Code
VS Code 中的使用限制
2976×1924 273 KB Usage limits in Copilot CLI
If you are approaching a limit, there are a few things you can do to help reduce the chances of hitting it:
- Use a model with a smaller multiplier for simpler tasks. The larger the multiplier, the faster you will hit the limit.
- Consider upgrading to Pro+ if you are on a Pro plan to raise your limit by over 5X.
- Use plan mode (VS Code, Copilot CLI) to improve task efficiency. Plan mode also improves task success.
- Reduce parallel workflows. Tools such as
/fleetwill result in higher token consumption and should be used sparingly if you are nearing your limits.
Why we’re doing this
We’ve seen usage intensify for all users as they realize the value of agents and subagents in tackling complex coding problems. These long-running, parallelized workflows can yield great value, but they have also challenged our infrastructure and pricing structure: it’s now common for a handful of requests to incur costs that exceed the plan price! These are our problems to solve. The actions we are taking today enable us to provide the best possible experience for existing users while we develop a more sustainable solution.
网友解答：--【壹】--：
太多人薅羊毛了，之前很多通过ask users tool来实现一次premium request无限token的，可惜了，现在还加上了周限额和月限额，彻底废了
--【贰】--：
幸好之前上车了，可惜没有用小号订阅，这个订阅把我的学生优惠挤掉了
--【叁】--：
能理解，但很心痛
直接关门不让订阅，这也太狠了
--【肆】--：
苹果土区还能订阅吗，最近没啥能用了唉
--【伍】--：
看来是真的不让用opus了啊。。A-真的。。。
--【陆】--：
我是真吐了啊 刚买的 pro，才用两下子 opus，就突然没了
--【柒】--：
限制越来越大了，之前是限制学生pro套餐不能指定高级模型
--【捌】--：
我就说怎么不能用了，这么好用的opus4.6不给用了 而且开始限制速率
--【玖】--：
好像可以退款，试试
0ccbb148c366da876e6ed21503e263ad1359×275 27.3 KB
--【拾】--：
现在限额限的太狠了。动不动就触发 weekly_rate_limited
--【拾壹】--：
我凌晨刚获批的学生包现在也不能用copilot pro了吗
image537×926 30.5 KB
image2198×800 191 KB
本文由 简悦 SimpRead 转码， 原文地址 github.blog
We’re making these changes to ensure a reliable and predictable experience for existing customers.
1200×630 61.4 KB
Today we’re making the following changes to GitHub Copilot’s Individual plans to protect the experience for existing customers: pausing new sign-ups, tightening usage limits, and adjusting model availability. We know these changes are disruptive, and we want to be clear about why we’re making them and how they will affect you.
今天，我们正在对 GitHub Copilot 的个人计划进行以下变更，以保护现有客户的体验：暂停新注册、收紧使用限制和调整模型可用性。我们知道这些变更具有破坏性，我们希望清楚地说明我们为什么要做这些变更，以及它们将如何影响您。
Agentic workflows have fundamentally changed Copilot’s compute demands. Long-running, parallelized sessions now regularly consume far more resources than the original plan structure was built to support. As Copilot’s agentic capabilities have expanded rapidly, agents are doing more work, and more customers are hitting usage limits designed to maintain service reliability. Without further action, service quality degrades for everyone.
代理工作流从根本上改变了 Copilot 的计算需求。长时间运行的并行会话现在经常消耗的资源远远超过最初计划结构所支持的。随着 Copilot 的代理能力快速扩展，代理正在做更多工作，更多客户正在达到为维持服务可靠性而设计的使用限制。如果不采取进一步行动，每个人的服务质量都会下降。
We’ve heard your frustrations about usage limits and model availability, and we need to do a better job communicating the guardrails we are adding—here’s what’s changing and why.
我们听说了您对使用限制和模型可用性的不满，我们需要更好地传达我们正在添加的护栏------以下是变化的内容和原因。
- New sign-ups for GitHub Copilot Pro, Pro+, and Student plans are paused. Pausing sign-ups allows us to serve existing customers more effectively.
GitHub Copilot Pro、Pro+ 和 Student 计划的新注册将被暂停。暂停注册使我们能够更有效地为现有客户服务。 - We are tightening usage limits for individual plans. Pro+ plans offer more than 5X the limits of Pro. Users on the Pro plan who need higher limits can upgrade to Pro+. Usage limits are now displayed in VS Code and Copilot CLI to make it easier for you to avoid hitting these limits.
我们正在收紧各个计划的使用限制。Pro+ 计划提供的限制超过 Pro 的 5 倍。需要更高限制的 Pro 计划用户可以升级到 Pro+。使用限制现在显示在 VS Code 和 Copilot CLI 中，以便您更容易避免达到这些限制。 - Opus models are no longer available in Pro plans. Opus 4.7 remains available in Pro+ plans. As we announced in our changelog, Opus 4.5 and Opus 4.6 will be removed from Pro+.
作品模型在 Pro 计划中不再可用。作品 4.7 在 Pro+ 计划中仍然可用。正如我们在变更日志中所宣布的，作品 4.5 和作品 4.6 将从 Pro+ 计划中移除。
These changes are necessary to ensure we can serve existing customers with a predictable experience. If you hit unexpected limits or these changes just don’t work for you, you can cancel your Pro or Pro+ subscription and you will not be charged for April usage. Please reach out to GitHub support between April 20 and May 20 for a refund.
这些变更是必要的，以确保我们能够以可预测的体验为现有客户提供服务。如果您达到了意想不到的限制，或者这些变更不适合您，您可以取消 Pro 或 Pro+ 订阅，并且不会收取四月份使用费。请在 4 月 20 日至 5 月 20 日期间联系 GitHub 支持部门申请退款。
How usage limits work in GitHub Copilot
使用限制如何在 GitHub 副驾驶中工作
GitHub Copilot has two usage limits today: session and weekly (7 day) limits. Both limits depend on two distinct factors—token consumption and the model’s multiplier.
GitHub Copilot 目前有两个使用限制：会话限制和每周 (7 天) 限制。这两个限制都取决于两个不同的因素------代币消耗和模型的乘数。
The session limits exist primarily to ensure that the service is not overloaded during periods of peak usage. They’re set so most users shouldn’t be impacted. Over time, these limits will be adjusted to balance reliability and demand. If you do encounter a session limit, you must wait until the usage window resets to resume using Copilot.
会话限制主要是为了确保服务在峰值使用期间不会过载。它们的设置是为了使大多数用户不会受到影响。随着时间的推移，这些限制将被调整，以平衡可靠性和需求。如果你确实遇到了会话限制，你必须等到使用窗口重置后才能恢复使用 Copilot。
Weekly limits represent a cap on the total number of tokens a user can consume during the week. We introduced weekly limits recently to control for parallelized, long-trajectory requests that often run for extended periods of time and result in prohibitively high costs.
每周限制代表了用户在一周内可以使用的代币总数的上限。我们最近引入了每周限制，以控制并行的、长时间运行的请求，这些请求通常需要长时间运行，并导致令人望而却步的高成本。
The weekly limits for each plan are also set so that most users will not be impacted. If you hit a weekly limit and have premium requests remaining, you can continue to use Copilot with Auto model selection. Model choice will be reenabled when the weekly period resets. If you are a Pro user, you can upgrade to Pro+ to increase your weekly limits. Pro+ includes over 5X the limits of Pro.
每个计划的每周限额也被设置，以确保大多数用户不会受到影响。如果您达到了每周限额，但仍有高级请求，您可以继续使用 Copilot 并进行自动型号选择。当每周期限重置时，型号选择将重新启用。如果您是 Pro 用户，您可以升级到 Pro+ 以增加您的每周限额。Pro+ 包含超过 5 倍的 Pro 限额。
Usage limits are separate from your premium request entitlements. Premium requests determine which models you can access and how many requests you can make. Usage limits, by contrast, are token-based guardrails that cap how many tokens you can consume within a given time window. You can have premium requests remaining and still hit a usage limit.
使用限制与您的高级请求权限是分开的。高级请求决定了您可以访问哪些型号以及可以发出多少请求。相比之下，使用限制是基于令牌的防护措施，它限制了您在给定时间窗口内可以使用的令牌数量。您可以保留高级请求，但仍然达到使用限制。
Avoiding surprise limits and improving our transparency
避免意外限制并提高我们的透明度
Starting today, VS Code and Copilot CLI both display your available usage when you’re approaching a limit. These changes are meant to help you avoid a surprise limit.
从今天开始，VS Code 和 Copilot CLI 都会在您接近限制时显示您的可用性。这些更改旨在帮助您避免意外的限制。
1394×1222 66.9 KBUsage limits in VS Code
VS Code 中的使用限制
2976×1924 273 KB Usage limits in Copilot CLI
If you are approaching a limit, there are a few things you can do to help reduce the chances of hitting it:
- Use a model with a smaller multiplier for simpler tasks. The larger the multiplier, the faster you will hit the limit.
- Consider upgrading to Pro+ if you are on a Pro plan to raise your limit by over 5X.
- Use plan mode (VS Code, Copilot CLI) to improve task efficiency. Plan mode also improves task success.
- Reduce parallel workflows. Tools such as
/fleetwill result in higher token consumption and should be used sparingly if you are nearing your limits.
Why we’re doing this
We’ve seen usage intensify for all users as they realize the value of agents and subagents in tackling complex coding problems. These long-running, parallelized workflows can yield great value, but they have also challenged our infrastructure and pricing structure: it’s now common for a handful of requests to incur costs that exceed the plan price! These are our problems to solve. The actions we are taking today enable us to provide the best possible experience for existing users while we develop a more sustainable solution.
网友解答：--【壹】--：
太多人薅羊毛了，之前很多通过ask users tool来实现一次premium request无限token的，可惜了，现在还加上了周限额和月限额，彻底废了
--【贰】--：
幸好之前上车了，可惜没有用小号订阅，这个订阅把我的学生优惠挤掉了
--【叁】--：
能理解，但很心痛
直接关门不让订阅，这也太狠了
--【肆】--：
苹果土区还能订阅吗，最近没啥能用了唉
--【伍】--：
看来是真的不让用opus了啊。。A-真的。。。
--【陆】--：
我是真吐了啊 刚买的 pro，才用两下子 opus，就突然没了
--【柒】--：
限制越来越大了，之前是限制学生pro套餐不能指定高级模型
--【捌】--：
我就说怎么不能用了，这么好用的opus4.6不给用了 而且开始限制速率
--【玖】--：
好像可以退款，试试
0ccbb148c366da876e6ed21503e263ad1359×275 27.3 KB
--【拾】--：
现在限额限的太狠了。动不动就触发 weekly_rate_limited
--【拾壹】--：
我凌晨刚获批的学生包现在也不能用copilot pro了吗