Copilot Usage Billing Is Live, and Code Review Now Spends Actions Minutes

AI 요약

• What happened: GitHub Copilot moved every plan to AI Credits usage billing on June 1, 2026.
  • The old premium request unit is being replaced by token usage mapped through model-specific rates, with 1 credit = $0.01.
• Cost change: Copilot code review now consumes both AI Credits and GitHub Actions minutes.
  • Private repository reviews spend Actions entitlement first, then standard Actions rates after included minutes are exhausted.
• Operator checklist: Teams need to review user budgets, cost center budgets, runner choices, and automatic review rulesets together.

GitHub Copilot's billing change moved from notice to production on June 1, 2026. In its June 1 changelog, GitHub said usage-based billing was live for all Copilot plans. The same update added a separate detail for engineering managers: Copilot code review consumes GitHub AI Credits and GitHub Actions minutes. The April 27 announcement told subscribers the change was coming. The June 1 update is the point where the billing system actually changed.

This is not a small wording change on the Copilot pricing page. It is GitHub moving away from a seat-plus-request model that fit editor completions and short chat sessions, then toward metering that can handle agentic workloads. A fast Copilot Chat question and a repository-aware code review agent running through a GitHub Actions workflow are different cost shapes. GitHub is now putting that distinction into the invoice.

GitHub's April 27 company blog post framed the change around Copilot's product shift. Copilot is no longer only an in-editor assistant; GitHub describes it as an agentic platform that can run long, multi-step coding sessions and use newer models. The old premium request model made a quick chat turn and a multi-hour autonomous coding session look too similar from a billing perspective.

The new unit is GitHub AI Credits. GitHub's Copilot billing documentation defines Copilot usage through AI credits, with one AI credit worth one cent. The models and pricing documentation explains the token accounting behind that unit. Input tokens, output tokens, and cached tokens are calculated against model-specific price tables, then converted into AI Credits. The more context, model time, and output an agentic task uses, the closer Copilot billing becomes to token accounting rather than request counting.

The base subscription prices remain in place. GitHub says Copilot Pro stays at $10, Pro+ at $39, Business at $19 per user, and Enterprise at $39 per user. Each plan now includes a monthly amount of AI Credits. Individual Pro includes $10 of credits with the $10 subscription, and Pro+ includes $39 of credits with the $39 subscription. Business and Enterprise also receive included credits aligned with the seat price. For existing Business and Enterprise customers, GitHub also announced promotional included usage from June through August 2026.

Some high-volume daily features are excluded from AI Credit usage on paid plans. GitHub says code completions and Next Edit suggestions do not consume AI Credits for paid Copilot users. That means the cost sensitivity of this change sits less on autocomplete and more on chat, agent mode, code review, and cloud agent workflows where repository context, tool use, and long sessions accumulate. A user treating Copilot as autocomplete and a user treating Copilot as an agent runtime can now produce visibly different bills.

The feature to watch first is Copilot code review. GitHub's April 27 changelog explained the execution model: the review agent uses an agentic tool-calling architecture, reads broader repository context, and runs through GitHub Actions. Starting June 1, every Copilot code review is billed through two mechanisms: AI Credits for model consumption and Actions minutes for the agent infrastructure.

The two-ledger structure has a technical boundary behind it. GitHub's models and pricing documentation says the token consumption of code review is charged as AI Credits. The agentic infrastructure that powers the review is charged as GitHub Actions minutes. In other words, model inference and runner execution are written to different accounting lines. AI Credits are associated with the review requester or, for automatic review policies, the pull request author. Actions minutes are attributed to the repository, enterprise, or cost center.

For private repositories, that becomes a budget issue immediately. GitHub's April changelog says each review in a private repository consumes the account or organization's existing Actions entitlement first. Once included minutes are exhausted, standard Actions rates apply. Public repositories keep free Actions minutes. The same code review request can therefore land in different places on the invoice depending on repository visibility and runner configuration.

GitHub also opened runner configuration for organization administrators. The June 1 changelog says admins can configure a default Actions runner for Copilot code review and apply it across repositories. The runner configuration documentation says the default is a standard GitHub-hosted runner. The same documentation allows self-hosted runners and larger GitHub-hosted runners. Larger runners can provide more performance, disk space, and Azure private networking, but they also carry higher per-minute rates.

Self-hosted runners add security and compatibility constraints. GitHub's documentation says Actions Runner Controller, or ARC, is the officially supported way to self-host Copilot code review runners. It warns against non-ARC self-hosted runners for security reasons and specifies Ubuntu x64 Linux runner compatibility. That matters because a code review agent may run with internal network reach and repository context. Cost optimization and network boundary design are now part of the same Copilot code review setting.

Automatic review configuration is also a cost setting. GitHub's automatic code review documentation describes ruleset-based setup. An organization or repository ruleset can automatically request a Copilot code review. The settings include whether to review every new push and whether to review draft pull requests. For developer experience, "review once" and "review every new push" look like similar automation options. Under usage-based billing, they create different numbers of model calls and runner executions.

Review effort level connects directly to spend as well. The same documentation lets a repository set the default review effort to low or medium. Medium review is described as deeper analysis for complex logic, security-sensitive code, and cross-service changes. GitHub also warns that medium reviews use more GitHub Actions minutes and AI Credits. It can be reasonable to use medium effort for high-risk changes. Applying medium to every pull request without observing usage will increase both token consumption and runner time.

Budget controls are the defensive layer for this billing change. GitHub's budgets for usage-based billing documentation separates user-level, cost center, and enterprise budgets. A user-level budget limits the AI Credits a user can consume during a billing cycle, and it acts as a hard stop in both the shared pool and metered phase. A $0 budget blocks that user immediately.

Cost center and enterprise budgets activate at a different point. GitHub says those budgets cap metered charges after the shared pool has been depleted. An enterprise budget is not a cap on the whole monthly invoice; it is a cap on metered usage after license fees. GitHub's example uses 400 Copilot Business licenses at $19 each, which produces $7,600 in license fees. Adding a $5,000 enterprise budget does not cap the bill at $5,000. It caps additional metered usage, making the maximum $12,600 before other charges.

One detail is easy for administrators to miss. GitHub's budget documentation says Stop usage when budget limit is reached applies only to enterprise spending limits and cost center budgets, and it is off by default. If that stop setting is disabled, charges can continue beyond the spending limit. User-level budgets behave differently: they are always hard stops. A team should not treat "we created a budget" and "usage will be blocked when the budget is reached" as the same statement.

Individual subscribers have an annual-plan exception. GitHub says monthly Pro and Pro+ users move automatically to usage-based billing on June 1, 2026. Annual Pro and Pro+ users remain on premium request-based pricing until the annual plan ends, although model multipliers for annual subscribers changed on June 1. After an annual plan expires, the user moves to Copilot Free and can upgrade to a paid monthly plan.

Community reactions focused on predictability. Threads on Reddit's r/GithubCopilot asked whether a plan that includes credits equal to the monthly subscription is meaningfully different from bringing an API key. Heavy chat and agent users worried about larger bills. Several commenters also found it confusing that code review spends both AI Credits and Actions minutes. Some comments use informal token estimates or personal usage math, so their exact numbers should not be generalized. The direction of the concern, however, matches the official structure: long agentic work is harder to reason about than a flat request allowance.

For enterprise teams, the first operational task is to list repositories where Copilot code review is enabled. Automatic review rulesets, draft pull request review, review-on-new-push settings, and medium effort should be treated as billing controls. A review that runs once per pull request and a review that runs after every push are both "automatic review" in the UI, but they are different workloads in Actions minutes and token usage.

The second task is usage visibility. GitHub's model pricing documentation says Actions usage for code review can be inspected by filtering GitHub Actions metrics for the copilot-pull-request-reviewer workflow. In the billing usage report, teams can filter by the dynamic/agents/copilot-pull-request-reviewer workflow path. Engineering managers need those identifiers before finance teams see a surprise line item. The source of spend may be Copilot overall, one repository's automatic reviews, review effort level, or runner choice.

The third task is runner policy. A team needs to decide whether the default GitHub-hosted runner is enough, whether a larger hosted runner is justified, or whether an ARC-managed self-hosted runner is required. Larger runners may reduce review latency but increase per-minute cost. Self-hosted runners bring network access and security questions. GitHub's runner documentation lists firewall allowlist entries such as api.githubcopilot.com, uploads.github.com, and user-images.githubusercontent.com, another sign that Copilot code review now behaves more like an operational workflow than a chat feature.

The fourth task is to document budget hierarchy. Enterprise budgets, cost center budgets, universal user-level budgets, and individual user-level budgets operate across different scopes and phases. A user-level budget can block a user even while shared pool credits remain. A cost center budget only matters after the shared pool is exhausted and metered usage begins. If finance creates caps while engineering enables automatic review, both teams need a shared definition of "block," "pool," and "metered usage."

This is not only a GitHub pricing story. Cursor, Windsurf, Claude Code, Gemini Code Assist, and other coding tools are also selling longer agentic coding sessions. Buyers will compare what a monthly subscription covers, whether overage is metered by tokens or requests, and whether tool execution or sandbox time is billed separately. GitHub's advantage is that code, pull requests, Actions, and billing sit inside one platform. The tradeoff is that code review costs now appear through both an AI ledger and an Actions ledger.

Copilot's new billing structure says agentic coding can no longer be measured as "a few chat requests." Model tokens, repository context, tool calls, runner execution, and review repetition policies all create cost. GitHub separating AI Credits from Actions minutes is a pricing decision that reflects that execution model. Development teams do not need to jump straight to disabling Copilot. They first need to know which automation runs in which repository, how often it runs, and which budget or entitlement it consumes.

After June 1, the operating question for Copilot teams changed. "Do we have Copilot licenses?" is less precise than "Who is spending AI Credits, which repositories are spending Actions minutes, and what gets blocked after a budget is reached?" Automatic code review may improve pull request quality, but under usage-based billing it is not only the addition of another reviewer. It is the addition of a metered workflow.

Sources

• GitHub Blog, GitHub Copilot is moving to usage-based billing.
• GitHub Changelog, Updates to GitHub Copilot billing and plans.
• GitHub Changelog, GitHub Copilot code review will start consuming GitHub Actions minutes on June 1, 2026.
• GitHub Docs, GitHub Copilot billing.
• GitHub Docs, Models and pricing for GitHub Copilot.
• GitHub Docs, Budgets for usage-based billing.
• GitHub Docs, Configuring runners for GitHub Copilot code review.