GitHub announced in April that its Copilot service would move from a request‑based subscription model to a usage‑based pricing structure, and the change went live today. The company now allocates a set number of AI credits to each paid tier, with one credit equating to one cent of compute. The $10‑per‑month Pro plan comes with 1,500 credits, the $39 Pro+ tier includes 7,000 credits, and the $100 Copilot Max level grants 20,000 credits. Subscribers also receive bonus credits tied to their plan, but the overall pool remains finite.
Developers who have relied on Copilot for everything from quick code snippets to multi‑hour autonomous coding sessions are reacting with surprise. On Reddit, Twitter and developer forums, users posted screenshots showing that a few hours of AI‑assisted coding can deplete a substantial portion of their monthly credits. In some cases, participants reported using up an entire month’s allowance in less than a day.
The shift marks a stark contrast to the previous model, which allotted a certain number of “requests” and “premium requests” based on the subscriber’s tier. Under that system, GitHub absorbed much of the rising inference cost, meaning a brief chat query and an extended coding session cost the same to the user. Analysts note that the new framework could expose heavy users to bills that would have run into the thousands of dollars under the current credit rates.
GitHub’s own pricing tool allows users to estimate how many credits a given workload would consume. Early adopters have run the calculator against their historic usage and found that their typical month‑long consumption would translate to a bill far exceeding the $10‑$100 price points they currently pay. The company has not disclosed whether it will adjust credit allocations or introduce higher‑tier plans to accommodate power users.
While the usage‑based model aligns Copilot’s revenue more closely with actual compute consumption, many developers worry about the impact on productivity budgets. Small teams and individual contributors, who previously counted on the predictable request limits, now face the prospect of monitoring credit usage in real time. Some have begun to explore alternative AI coding assistants or to scale back reliance on Copilot until the pricing model stabilizes.
GitHub has not indicated a timeline for revisiting the credit structure, but the outcry suggests that the company will need to address the concerns of a community that has grown increasingly dependent on AI‑driven development tools.
This article was written with the assistance of AI.
News Factory SEO helps you automate news content for your site.