GitHub pauses Copilot sign-ups due to compute costs

GitHub Copilot went from: "We can't take new users." To: "Pay per use." That's not a pricing update. That's a signal. When a product is capacity-constrained, it means demand outran infrastructure. That's a good problem. But it also means the old pricing model, flat subscription, unlimited usage, stopped making sense. Because some users were using a little. And some were using everything. Usage-based billing fixes that. The heavy users pay more. The light users pay less. The economics align with the value actually being delivered. But here's the more interesting implication. When AI coding tools move to usage-based pricing, the conversation inside every engineering org shifts. It's no longer "do we have Copilot?" It's "how much are we actually using it — and is the output worth what we're paying?" That's a harder question. And a healthier one. The teams that use it constantly and ship faster will justify the cost easily. The teams that had it running in the background, barely touched, on a flat subscription? Now they have to reckon with whether AI actually changed how they work. Or just felt like it did. Usage-based pricing doesn't just change what you pay. It forces honesty about what you got. #GitHub #Copilot #AI #Engineering #FutureOfWork

GitHub has paused new Copilot sign-ups and tightened usage limits for existing users because AI coding demand is overwhelming its compute capacity. The pause affects individual Copilot plans and reflects the raw infrastructure cost of running AI-assisted development at scale. GitHub Copilot has become one of the most widely adopted AI tools in software engineering, and the fact that Microsoft-backed GitHub cannot keep up with demand is a telling signal about where the AI compute bottleneck really sits. This is not just a supply issue. It is a strategic vulnerability for every engineering organization that has built Copilot into its development workflow. When your productivity tool becomes capacity-constrained, your team's velocity drops with it. For engineering leaders, this should prompt a serious conversation about single-tool dependency for AI-assisted coding. If the platform you rely on can pause sign-ups without warning, your development pipeline is more fragile than you thought. #GitHubCopilot ♻️ Repost if you think someone in your network should see this. 🌤️ Follow for daily enterprise IT news.

The era of "all you can consume" AI for developers is officially ending. Woke up to the news yesterday that GitHub Copilot starting June 1, 2026... is moving to usage-based billing. While Claude Code, Cursor and other tools have also followed. It's a fundamental shift in how we build with agents. I posed about this last year that the subsidization of LLM costs was not going to last too long. Here we are now, the compute demands have become unsustainable. A single agentic loop can burn more tokens than a developer used in an entire month under the old flat-rate model. For copilot this is what it will look like from June: - "Unlimited" is replaced by credits: Your $10/mo plan now gives you exactly $10 in "GitHub AI Credits." (Personal observation, I consume $10 easily in a 6-8 hours of use with Sonnet on Copilot) - Token-based billing: You’re paying for every input, output, and cached token you consume. - Code reviews will take from that budget and will also consume github runner minutes. Double whammy there. Why does this matter? Because it forces a move toward what I call "Efficient Agency." The old model, a good agent was one that eventually found the answer, regardless of how many tokens it burned. The new eval benchmark for the future will be solving the problem with the absolute minimum number of tokens. However I dont think this is a bad thing. This shift will finally flush out the "wasteful" agents that just loop until they hit a context limit. It's going to reward engineering craftsmanship over "vibe coding" loops. P.S. At Optimal AI, we’ve been obsessing over this for a while. We use smart model routing and multi-model techniques to keep quality high while keeping costs drastically lower. This is how we can continue to provide unlimited-style value in a usage-based world. #GitHubCopilot #AIEfficiency #EngineeringLeadership #LLMOps #OptimalAI

GitHub Copilot is moving to Usage-Based Billing GitHub just announced that starting June 1 2026, Copilot will transition to a usage-based model powered by GitHub AI Credits. A few important details: ✦ Credits over Requests: Subscriptions now include a monthly credit allotment. Usage is calculated via tokens (Input/Output/Cached), similar to standard LLM APIs. ✦ Core features remain included: Standard code completions and “Next Edit” suggestions will not consume credits. ✦ Pooled Usage for Teams: Organizations can now pool credits across seats to eliminate wasted capacity and set granular budget caps. Why it matters: Base prices aren't changing, but the ceiling is lifting. This move enables more heavy-duty, agentic workflows while giving engineering leaders better transparency into their actual AI ROI. it’s time to start looking at those usage dashboards! 🙂 Full details here: https://lnkd.in/dUa-8hDU #GitHub #Copilot #GenAI #SoftwareEngineering #AI #DevOps

As some of you have suspected (Boris Cherkasky gets the credit in my feed) — GitHub's recent availability struggles are a direct consequence of AI coding tools using it as infrastructure at massive scale. And this raises some genuinely interesting questions, both on the product/business side and the engineering side. GitHub's COO wrote "we can't just scale horizontally and vertically" (https://lnkd.in/dbXJehWs) — and that's true in a deep way. Even a system built for scaling eventually hits new bottlenecks. You can add more workers, but the queue that feeds them has its own throughput ceiling. The small service that checks permissions before a GH Action runs, the one that watches for abuse, the one that validates... — each of them needs to grow, and each at a different rate. That's a genuinely complex and fascinating engineering problem (and I'd love to read a proper writeup on how they're tackling it). But there's a second problem — a business one. How do you price the services to cover the costs for an infrastructure that's growing at this rate? Usage patterns are shifting dramatically (of course I don't have data on how). It might be the ratio of paying to free users, or the amount of code per average seat, or the number of Actions triggered (more repos = more pipelines, more commits == more pipleines). If the story is "a huge volume of small free users," the answer is probably one thing — I'd guess tightening the free tier. But if the story is that usage *patterns* themselves have fundamentally changed (which is my suspicion), then the answer has to be more nuanced and might be painful for long time users and organizations. I genuinely hope GitHub figures out the engineering side first — running more for less — before they're forced to solve it on the business side, which means charging all of us more. The AI coding wave is real (for now at least, while the VC money that powers it doesn't run up). The infrastructure stress it creates is real. The answers? less clear currently. it's not SaaSpocalypse but the changing usage patterns would enforce change and adaptions

GitHub was designed for humans. AI agents are breaking it. I ran a batch of 40 AI coding agents against a single GitHub repo last week. Within 90 seconds: rate-limited, merge conflicts on every branch, and three token revocations. The architecture assumes a human opens a PR, waits, reviews, merges. Agents don't wait. Cloudflare just shipped a Git platform built for this exact problem. 𝗧𝗛𝗘 𝗕𝗢𝗧𝗧𝗟𝗘𝗡𝗘𝗖𝗞: GitHub's API rate limits and merge queue assume sequential human workflows — agents operate in parallel at machine speed 𝗧𝗛𝗘 𝗦𝗛𝗜𝗙𝗧: Cloudflare's platform treats concurrent writes, branch isolation, and agent-scoped auth as first-class primitives, not afterthoughts 𝗧𝗛𝗘 𝗦𝗜𝗚𝗡𝗔𝗟: Every major cloud provider is building agent-native infra — the tools we built for human developers don't scale to autonomous ones 𝗧𝗛𝗘 𝗤𝗨𝗘𝗦𝗧𝗜𝗢𝗡: How long before your CI/CD pipeline has more agent committers than human ones? If you're running AI coding agents at any scale, the GitHub bottleneck is real. This isn't about replacing GitHub for human workflows — it's about recognizing that agent workflows need purpose-built infrastructure. Anyone else hitting GitHub's walls with agent workloads? Curious what workarounds you've found. Full code + walkthrough → cloudedventures.com #AIAgents #DevOps #CloudEngineering #GitHub #Cloudflare

I've been observing the evolution of AI tooling pricing, and this week's GitHub announcement marks a significant turning point worth discussing. Starting June 1, 2026, GitHub Copilot will transition to usage-based billing, replacing the flat-rate premium request model with GitHub AI Credits based on token consumption. While this may seem like a straightforward pricing update, it reflects a more fundamental shift in the AI tooling cycle. Initially, Copilot served as an autocomplete assistant—smart and useful, but with predictable compute demands, making flat-rate pricing reasonable. Today, Copilot has evolved into an agentic platform capable of conducting autonomous multi-hour coding sessions, reasoning across entire codebases, and tackling complex problems with minimal human input. The compute costs associated with this level of functionality far exceed those of quick code suggestions. GitHub has absorbed the cost gap for years, and the move to usage-based billing is a necessary correction. The fallback model is no longer available. Previously, when premium requests were exhausted, teams could downgrade to a cheaper model and continue working. Starting June 1, running out of credits will result in a hard stop unless additional credits are purchased or admin budget controls permit continued access. This represents a significant operational change for teams engaged in heavy agentic workflows. The preview billing window in early May is crucial. GitHub is providing admins with visibility into projected costs before the transition, making this preview period essential for any team with substantial Copilot usage. The pooled credits model for enterprises is a smart design. It allows organisations to pool unused credits across teams, preventing stranded capacity and offering finance teams a clearer overview of usage. Pricing remains unchanged: Pro at $10, Business at $19, and Enterprise at $39, with included credits matching these prices. For light to moderate users, the practical impact may be minimal. The organisations that build governance frameworks now will be better positioned than those that do it reactively. Follow @BuzzShift — Smart ideas. Zero fluff. ⚡ https://lnkd.in/gwCiuaZU Full details at the GitHub blog. 📌 Source: https://lnkd.in/guZYYryA #GitHub #Copilot #AI #EngineeringLeadership #AIStrategy #SoftwareDevelopment #DeveloperTools #FutureOfWork #TechLeadership #BuzzShift

Rising costs aren't just hitting the gas pump anymore—they’ve officially reached our IDEs. ⛽️💻 GitHub just confirmed a major shift: Starting June 1, 2026, Copilot is moving to usage-based billing with GitHub AI Credits.  While your monthly subscription price stays the same, it now acts as a credit limit. Once those tokens are gone, you’re paying for extra usage. Standard code completions remain free, but Copilot Chat and Agentic features (like the new Code Review) will now eat into your budget.  Context is the new currency. If you aren't managing your tokens, you’re burning money. Here is my "Token Diet" Plan to keep your dev speed high without breaking the bank: 📉 The GitHub AI Token Diet • Practice "Context Hygiene": Close your idle tabs! Copilot scans open files for context. Keeping 20+ tabs open sends a massive "context tax" with every request. Stick to a 3-5 tab rule. • Targeted Exclusions: Use .github/copilot-instructions.md or organizational settings to ignore "noisy" files—like minified JS, huge JSON datasets, or logs. If Copilot doesn’t index them, you don't pay for the tokens. • Feature Discipline: Ghost-text completions and Next Edit suggestions are free. Use them for the "easy" stuff. Save your AI Credits for complex logic, architecture, and debugging.  • Budget Guardrails: (For Admins) Credits are pooled in Enterprise. Set up Spend Notifications immediately. One dev running an agentic loop can drain a team’s monthly budget in a single afternoon.  • Prompt Caching: Don’t clear your chat history mid-problem. Re-using the same context session is significantly cheaper than starting a fresh conversation every 5 minutes. The "Metered AI" era is officially here. It’s time to stop treating prompts like they're free and start treating them like the infrastructure cost they actually are. 🚀 Are you ready for the switch, or is it time to look back at local LLMs for the basics? 💬👇 #GitHub #AI #SoftwareEngineering #Copilot #FinOps #TechTrends #Coding

GitHub Copilot Controversy Highlights Challenges in AI-Assisted Development The recent controversy surrounding GitHub Copilot and AI-generated pull request messages has sparked discussions about transparency and developer trust. As AI tools become more integrated into software development, maintaining clarity, accountability, and ethical use is becoming increasingly important. This case reflects the evolving dynamics between automation and human oversight in coding environments. 🔗 Read more: https://lnkd.in/gCkBBEPP #GitHub #Copilot #ArtificialIntelligence #SoftwareEngineering #DeveloperTools #TechIndustry #Innovation #TechGenyz

GitHub just reported that 51% of all code committed to its platform in early 2026 was generated or substantially assisted by AI. Think about that for a moment. A majority of commits to the world’s largest code host now have an AI somewhere in the loop. And we’re only 3 years out from GitHub Copilot’s general availability. The supporting data tells the same story: → McKinsey: AI coding tools cut routine coding time by 46% (4,500+ developers, 150 enterprises) → Stack Overflow: 84% of developers are using or planning to adopt AI coding tools → 20M+ GitHub Copilot users, with agent mode now standard But here’s what the headline misses: the developers seeing the biggest gains aren’t the ones who replaced their workflow with AI. They’re the ones who redesigned their workflow around AI. The 2026 developer stack isn’t one AI tool. It’s a combination: • Claude Code or Cursor for complex reasoning and multi-file edits • Copilot for line-level autocomplete • Local models (Ollama, Tabby) for sensitive or proprietary code The developers who treat AI as a single tool will plateau. The ones treating it as a new layer in their stack are the ones compounding. 51% of code is already there. The other 49% won’t wait long. #DeveloperProductivity #AITools #SoftwareEngineering #GitHub #FutureOfWork