GitHub Copilot switches to token-based billing June 1, some users report costs jumping from $50 to $3,000

GitHub Copilot Switches to Token-Based Billing

Microsoft's GitHub Copilot will transition from flat-rate subscription pricing to token-based billing on June 1, according to user reports. The change has prompted sharp criticism from developers who claim their monthly costs will increase dramatically.

Reported Price Increases

Multiple developers shared cost comparisons on Reddit and X:

• One user reported costs rising from approximately $29 per month to nearly $750
• Another posted a screenshot showing an increase from around $50 to $3,000 monthly
• Previous pricing: flat rate based on requests
• New model: charges based on token consumption during coding sessions

Developer Response Split

The community response has divided into three camps:

Critics of the change argue the price increases are prohibitive. "This new usage model is just stupidly expensive," one developer wrote. "At that cost, it is no longer cost-effective or useful in any practical way."

Defenders of the pricing claim the high costs reflect inefficient usage. "The only way it gets crazy like that is if you are purely 'vibe coding' with a ton of bloated iterations," one user commented, suggesting developers with proper workflows experience minimal overage charges. "It's pretty affordable for even small outfits if used as a tool."

Microsoft critics argue the company encouraged heavy usage of its AI coding assistant, then switched pricing models without adequate warning. "Microsoft provided this billing method and they kept making it easier and easier to burn through massive numbers of tokens on single premium requests that could churn for hours or even days while spawning dozens or even hundreds of sub-agents," one developer noted.

Subsidy Economics Unclear

The economics of GitHub Copilot's previous flat-rate model remain opaque. "Holy fuck how much money was copilot losing," one Reddit user asked. Microsoft has not disclosed how much the company subsidized the service under the old pricing structure.

Microsoft did not respond to requests for comment by publication time.

What This Means

This pricing shift follows a familiar pattern in AI services: attract users with heavily subsidized pricing, then transition to usage-based models once lock-in is established. The wide variance in reported cost increases—some users claiming minimal impact, others reporting 60x increases—suggests either dramatic differences in coding workflows or that Microsoft's previous model masked extremely high compute costs for certain usage patterns. The June 1 implementation date gives developers minimal time to adjust workflows or migrate to alternatives like Cursor, Cline, or other AI coding assistants.