GitHub Copilot to Shift to Token-Based Billing in June

GitHub will transition its Copilot AI coding assistant from premium request-count billing to a token-based pricing model starting June 1, 2026, the company announced.

The change means Copilot users will be charged based on actual token consumption rather than a set number of premium requests, according to The Decoder (https://the-decoder.com/github-copilot-switches-to-token-based-billing-in-june-2026/). The shift affects both individual developers and enterprise customers who rely on the AI pair-programming tool across their organizations.

GitHub Copilot, owned by Microsoft, is among the most broadly adopted AI coding assistants on the market, serving millions of developers worldwide. The pricing model change carries direct implications for US corporate software development budgets, particularly at enterprises that have scaled Copilot deployments across large engineering teams.

Token-based billing aligns GitHub’s approach with the pricing conventions already standard among major AI providers, where usage is metered by the volume of tokens — the units of text processed by large language models — consumed during interactions. The model can offer more granular cost tracking but may also introduce less predictable monthly expenses for heavy users.

The move comes as competition in the AI coding assistant market has intensified, with rivals including Cursor, Amazon Q Developer, and Google’s Gemini Code Assist all vying for developer adoption. Pricing strategy has become a key differentiator as enterprises evaluate which tools deliver the best return on investment.

For enterprise procurement teams, the transition will likely require updated budgeting frameworks and potentially new usage monitoring practices. Organizations with large developer populations may see costs fluctuate based on how actively engineers engage Copilot’s features, including code completion, chat, and agent-mode capabilities.

Microsoft has not disclosed specific per-token pricing rates ahead of the June 1 effective date. Developers and enterprise administrators should expect updated billing documentation from GitHub in the weeks leading up to the transition.