Copilot usage-based billing: No spending cap, no cost alerts, $549 bill on Free plan — individual power users need sustainable pricing

[lhfei]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Copilot Usage-Based Billing: Unsustainable Costs for Individual Power Users

Submitted by: Hefei Li (@lhfei)
Date: September 9, 2026
Current Plan: Copilot Free ($0/mo)
Related Support Ticket: #4667814

---

My Experience

I am a long-time GitHub user and individual developer on the Copilot Free plan ($0/mo). After the June 1, 2026 transition to usage-based billing, my August 2026 bill reached $548.99 — over 5x the price of Copilot Max ($100/mo), the highest individual tier available.

This charge was incurred through normal, good-faith software development work (code completion, chat, and agent mode) during regular working hours. I did not exploit any loophole, run automated scripts, or abuse the system in any way. I was simply using Copilot as intended.

I had no prior warning that the Free plan carries zero spending cap and zero included AI credits. Every single interaction was billed at full per-token rate with no upper limit. I was completely unaware that normal daily usage could accumulate to nearly $550 in a single billing cycle.

I have since stopped all Copilot usage (September 2026 usage is effectively $0) because the cost is prohibitive.

---

The Core Problem

The current pricing model has a fundamental structural flaw for individual developers:

1. NO SPENDING CAP — There is no mechanism to set a monthly maximum spend. A Free plan user can be billed unlimited amounts without any safeguard.

2. NO INCLUDED CREDITS ON FREE PLAN — Unlike Pro ($10/mo includes some credits) or Max ($100/mo includes 20,000 credits), the Free plan provides zero buffer. Every token is billed from dollar one.

3. NO HIGH-TIER INDIVIDUAL PLAN — Copilot Max at $100/mo is the ceiling. For power users whose usage exceeds this, there is no path forward — no committed-use discounts, no bulk credit packages, no custom pricing.

4. INSUFFICIENT TRANSITION COMMUNICATION — The April 28, 2026 announcement explained the billing change but did not adequately warn Free plan users about the specific risk of uncapped overage exposure.

5. COST DISPROPORTION — At ~$0.01/AI credit, heavy daily usage with agent mode and premium models quickly generates bills that exceed what most individual developers can justify — with no predictability or control.

---

What I Am Requesting

1. MONTHLY SPENDING CAP — Allow all users (especially Free plan) to set a hard monthly spending limit. Once reached, Copilot should gracefully pause until the next cycle.

2. USAGE ALERTS / THRESHOLD NOTIFICATIONS — Send email or in-app alerts when usage reaches 50%, 75%, and 90% of a user-defined budget.

3. HIGHER-TIER INDIVIDUAL PLAN — Introduce a plan above Copilot Max (e.g., "Copilot Ultra" at $200–300/mo) with proportionally more included credits for individual power users.

4. COMMITTED-USE DISCOUNTS OR BULK CREDIT PACKAGES — Allow individual developers to pre-purchase AI credits at a discount (similar to AWS Reserved Instances).

5. ONE-TIME WAIVER FOR FIRST-CYCLE OVERAGE — For users whose first billing cycle under the new model produced unexpectedly high charges, offer a one-time courtesy waiver or reduction.

6. REAL-TIME COST ESTIMATOR IN IDE — Show running cost of the current session so developers can see expenses before they become a bill.

---

Why This Matters Beyond Me

I am not an isolated case. Based on community reports since June 2026:

• Multiple developers have reported bills ranging from $750 to $3,000/month
• An 80-person company calculated their new monthly Copilot spend equals one full-time engineer's annual salary
• Reddit and Hacker News threads are filled with developers expressing shock at their first usage-based bills
• The lack of spending caps is the single most complained-about aspect of the new billing model

If GitHub does not address these concerns, individual developers — the backbone of the GitHub ecosystem — will migrate to alternatives (Cursor, Claude Code, Continue + local models, Amazon Q Developer) that offer better cost predictability.

---

Closing

I have been a loyal GitHub user for years. I do not want to leave. But I cannot use a tool that exposes me to uncapped financial risk with no controls, no alerts, and no affordable tier for my usage level.

Please escalate this feedback to the Copilot Product and Pricing team. These are not edge cases — they are systemic issues affecting a growing number of individual developers.

Thank you for reading.

— Hefei Li (@lhfei), September 9, 2026``

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[lhfei]

UPDATE (September 9, 2026): After correspondence with GitHub Support,
I want to correct and clarify several points in my original post:

1. I was NOT on the Free plan during the billing period in question.
   I subscribed to Copilot Pro Plus on July 27, 2026, and upgraded
   to Copilot Max on August 5, 2026. The subscription was cancelled
   on August 15, 2026, with a prorated refund of $87.10.

2. A spending budget feature DOES exist in GitHub's billing settings.
   A $550 budget was created on my account on August 10, 2026. However,
   this was FIVE DAYS after upgrading to Max, meaning my account had
   no spending protection during the initial high-usage period.

3. The core issues I raised remain valid:

   • Spending caps are NOT enabled by default — users must discover
     and configure them manually
   • There is no individual plan above Copilot Max ($100/mo) for power
     users whose usage exceeds 20,000 AI credits
   • The transition from fixed-price to usage-based billing caught
     many developers (myself included) unprepared for the cost implications
   • Default settings should protect users from uncapped overage exposure

I apologize for the inaccuracies in my original post and appreciate
GitHub Support's transparency in clarifying the facts. My feedback
about improving default protections and pricing tiers for individual
developers stands.

[sunmeat]

Thank you for raising this detailed feedback, @lhfei. You have highlighted a critical gap in the current billing model for individual power users—especially regarding agentic mode, which silently inflates token consumption due to multi-turn context loops and tool-use retries.

While the GitHub Copilot Product and Pricing teams evaluate feature requests like hard spending limits and budget alerts, here are immediate mitigation steps and technical strategies to protect against unexpected usage-based charges:

1. Immediate Actions & Billing Support
   File a Billing Dispute for a One-Time Courtesy Waiver: Open a ticket at support.github.com under Billing / Financial Support explicitly citing "First-cycle overage under the new usage-based model without prior budget warning." GitHub Support frequently evaluates unexpected multi-hundred-dollar first-month spikes on a case-by-case basis for one-time credits.

Disable Copilot Agent Mode in IDE Settings: Agent mode consumes up to 10x–20x more tokens than standard inline autocomplete because it repeatedly sends entire project trees, terminal outputs, and intermediate planning steps to the model. Switch back to standard completion or basic chat while usage-based tracking is active.

Manage Model Selection: In VS Code / JetBrains, explicitly select smaller base models (e.g., standard Claude Sonnet or GPT-4o mini variants) rather than deep reasoning / high-tier extended-thinking models that charge significantly higher per-token input/output rates.

2. Setting Up Self-Managed Guardrails & Local Options
   Until GitHub natively implements hard budget caps and IDE cost estimators, individual power users can maintain cost predictability using these methods:

Switch to Open-Source / Local Extensions: Extensions like Continue.dev allow you to plug in your own API keys (where hard spending limits can be set via OpenAI / Anthropic / OpenRouter dashboards) or route directly to local LLMs via LM Studio / Ollama for $0 per token.

Proactive Context Management: Avoid leaving large multi-file contexts or massive terminal outputs open in agent sessions, as every subsequent prompt re-sends the entire history payload back to the billing endpoint.

Your structured feedback regarding hard spending caps, 50%/75%/90% threshold notifications, and dedicated power-user tiers is vital for the platform's individual developer ecosystem. Upvoted for visibility!