GitHub Copilot is not the same product it was a year ago. It has evolved from an in-editor assistant into an agentic platform capable of running long, multi-step coding sessions, and agentic usage is becoming the default . That evolution just got expensive.
On June 1, GitHub switched all Copilot plans to usage-based billing, replacing premium requests with GitHub AI Credits calculated on token consumption . The base price stayed at $10 per month for Pro subscribers. But users are now charged based on how many tokens they burn through as they work, and some developers have taken to Reddit and X to bemoan what appears to be a drastic escalation in cost . One Pro user reported their monthly allotment exhausted in a single session on June 1, when historically the plan lasted the entire month .
The timing is striking. By January 2026, 74% of developers worldwide had already adopted specialized AI tools for developers — not just chatbots like ChatGPT . That figure climbed to 84% by mid-year, with 62% relying on at least one AI coding assistant, agent, or code editor . But just as the market reached saturation, the economics shifted beneath it.
Can the Flat-Rate Model Survive Agentic Workflows?
GitHub has absorbed much of the escalating inference cost behind agentic usage, but the current premium request model is no longer sustainable. Usage-based billing fixes that by better aligning pricing with actual usage , the company said in April.
The problem is predictability. Token-heavy workflows such as chat, agentic coding sessions and code review are likely to become more cost-sensitive, and user comments raised concerns about reduced included value, less predictable usage, and whether Copilot remains competitive with direct model APIs and rival coding tools .
GitHub Copilot's share among professional developers fell from 67% to 51% between late 2025 and early 2026, according to the Stack Overflow Developer Survey. In the same period, Cursor debuted at 18% adoption, while Claude Code reached 10%. The JetBrains survey showed even tighter numbers: Copilot 29%, Cursor 18%, Claude Code 18% .
The shift is not just about pricing. Claude Code is continuing to rapidly grow in awareness, adoption, and admiration. 57% of developers had heard of it in January 2026, and 18% currently use it at work — a 1.5x increase from September 2025 and 6x increase from roughly 3% in April–June 2025 . It also has the highest product loyalty metrics on the market, with a CSAT of 91% and an NPS of 54 .
Cursor's trajectory is even sharper. Anysphere, the company behind Cursor, went through an unprecedented revenue trajectory in 2025, with revenue doubling every two months between June 2025 and February 2026. Cursor's ARR went from $100 million in January 2025 to $500 million in June, $1 billion in November, and $2 billion by February 2026 — faster than any other B2B SaaS company had ever reached $2 billion in ARR .
What Happens When the Government Pulls Your Model?
Three days after Anthropic launched Claude Fable 5 on June 9, the model vanished. Anthropic disabled Claude Fable 5 and Claude Mythos 5 on June 12, 2026, to comply with a US government export-control directive. The order, citing national security authorities, suspends access for any foreign national, and the practical result is a global shutdown of both models for all customers .
Fable 5 leads SWE-bench Verified at 95.0% and SWE-bench Pro at 80.3%, but Fable 5 and Mythos 5 are export-suspended as of June 12, so most users cannot run them today . The government cited a national security concern over a "jailbreak" technique that lets the model read a codebase and identify software vulnerabilities. Anthropic argues the technique is narrow, already known, and present in other public models .
The disruption was immediate. South Korea was among the most active markets for Claude globally, with NAVER, Samsung SDS, LG CNS, and SK Hynix all deploying the platform at scale. The export control directive specifically named Korean institutional access as revoked following June 12. All of those deployments went dark the same night .
As of June 27, fifteen days after the suspension, Anthropic posted an official update: the government notified them that Mythos 5 can be redeployed to a set of US organizations that operate and defend critical infrastructure. They're restoring access for these organizations quickly, and continuing to work with the government to expand access to Mythos 5 and make Fable 5 available for general use again . But for most developers, the model remains offline.
The incident exposed a category of risk most teams had not priced in. Organizations that had embedded Fable 5 into production workflows faced immediate operational disruption when the model was suspended. Critically, that disruption was not caused by a security incident in their own environment, a vendor infrastructure outage, or a contractual dispute. It was caused by a government regulatory action that Anthropic itself contested and did not control .
