Change history

GitHub Copilot limit changes

Current and previous observations remain linked to their official sources. Detection date and effective date are kept separate when known.

Verified Aug 22, 20260 verified changes

Verified history

No verified historical change is recorded yet.
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean GitHub Copilot has never changed. Undated values are kept in the current baseline below instead of being presented as history.

Current monitored baseline

HyperObserve currently monitors 3 scoped observations for GitHub Copilot. The baseline covers monthly premium requests, monthly reset, code review multiplier. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.

ConstraintCurrent valueScopeVerified source
monthly premium requestsOther plans receive monthly GitHub AI Credits instead: Pro 1,500, Pro+ 7,000, Max 20,000, where one credit equals $0.01.Legacy annual Pro: 300; Pro+: 1,500 per monthAnnual Pro/Pro+ on legacy request-based billing (after 2026-06-01)GitHubSep 17, 2026
monthly resetBoth legacy premium requests and GitHub AI Credits reset at 00:00:00 UTC on the first day of each calendar month; unused allowance is forfeited.1st of each month at 00:00:00 UTCLegacy request-based billing and GitHub AI CreditsGitHubSep 17, 2026
code review multiplierUnder usage-based billing, code review is charged in AI credits by tokens plus GitHub Actions minutes rather than a fixed multiplier.13 premium requests per reviewLegacy annual Pro/Pro+ plansGitHubSep 17, 2026

Tracked constraints and impact

Premium request quotas, reset timing, model multipliers, and service throttling. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.

How a change is verified

  1. Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
  2. Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
  3. Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.

Official sources monitored

These first-party documents support the current GitHub Copilot baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.

Requests in GitHub Copilot (legacy request-based billing)

Legacy premium request allowances and monthly reset; applies to annual Pro/Pro+ plans after June 1, 2026

Model multipliers for annual plans on request-based billing (legacy)

Copilot code review multiplier of 13 on legacy annual plans

Related

Continue researching GitHub Copilot