I'm out... Never again untill plans change again.

[nuttyproducer]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I am extremely disappointed with the new Copilot pricing changes, and I’ve decided to stop using the product entirely.

The value proposition has clearly shifted in a way that feels out of touch with actual developers. What was once an accessible, productivity-enhancing tool now feels like it’s being aggressively monetized without a corresponding increase in value. As someone who actively builds, experiments, and integrates AI into real workflows, this change doesn’t just feel inconvenient—it feels like a breach of trust.

Pricing changes are understandable in principle, but the way this has been handled makes it hard to justify continued use. It sends the message that long-term users and early adopters are not being considered. Tools like Copilot succeed because developers choose to integrate them deeply into their workflow. When that relationship is disrupted, it’s not easy to rebuild.

As a result, I will not only be discontinuing my usage, but I will also no longer recommend Copilot to others. In fact, I’ll actively encourage developers in my network to explore alternatives that offer more transparent and sustainable pricing models.

That said, I genuinely hope you reconsider this direction. There is still an opportunity to rebuild trust with your developer community, but it requires listening to feedback and aligning your pricing with real-world usage and expectations.

Until then, I’m out.

[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. ⭐

[alexmatthewman]

They killed it for me too. It's efforty but not ridiculous to just build your own local AI copilot. The whole point of their offering was that it was cheap and low effort. They've removed the cheap part so guess what....I'll build my own, with blackjack.

[nuttyproducer]

This was for me the only affordable way to get some work done... Really... If i was a lot more wealthy I would consider it still. So they take away the pleasure and creativity of people that want to get ahead in life too I guess... Well i'm totally out. I'm going to deepseek and i don't even care if china is taking my information.

[nuttyproducer]

Let's all open cases like this and let's spend some copilot bot tokens for free :D Motherf'ers

[moonlune]

At this stage, one of the only solutions is to redirect requests from the software or its configuration to a local model or a relatively inexpensive remote model!

[nuttyproducer]

That's what I will be doing tomorrow. Even though I don't have heavy computing power in my house, i will go to seek help from Deepseek 👯

For now, I just hope our protest can shed some light on their ridiculous changes... Not that they care much ofcourse... But it needs to be done!

How did you manage the switch, or are you going to manage a switch? Let's see what we can come up with, i will share my updates!

I need to go to my windows PC eventually because my late 2013 macbook doesn't allow me to update VScode, so I can not use the newest extensions that can provide me with running deepseek V4 within the same IDE, agent calls, reasoning etc...

[moonlune]

I wrote a program myself to forward Ollama requests to any cloud service provider. At this stage, I’ve only implemented DeepSeek (since I don’t have accounts with many other model providers, services like Cloude might also work). Qwen has its own technical requirements, so it might not work in Visual Studio yet. The thing is, DeepSeek is really cheap—I tested a simple query and it only cost $0.0133!

[mo0feng]

You can search for the DeepSeek V4 for Copilot Chat plugin in VS Code. It can continue your current Copilot session, keeping skills and MCP unaffected until you switch to Cline or Kilo.

[KaiXuanSama]

It's quite a coincidence — I'm also doing the same thing. I'm using the SpringBoot backend because I'm more familiar with it. I support some relatively niche providers, but for the popular ones, I support DeepSeek and Mimo. DeepSeek is relatively cheap, and Mimo gave me a credit of 840e, so I'm very willing to use them.

很凑巧，我也在做相同的事，我使用的是SpringBoot后端，因为我对他更加熟悉，并且我支持一部分相对冷门的供应商，但热门的能够支持deepseek和mimo，因为ds相对便宜，而mimo，他们送了我840e的额度，我很愿意使用他们

[Usman-Amin-AI]

Thank you for taking the time to share your feedback.

I understand your frustration regarding the recent Copilot pricing changes. Pricing adjustments can have a significant impact on developers who have integrated a tool deeply into their daily workflows, and it's understandable that such changes may alter the perceived value of the product.

Your feedback highlights several important concerns, including affordability, transparency, trust, and the expectations of long-term users. These are valuable points for the GitHub team to consider, particularly because the success of developer tools depends heavily on maintaining strong relationships with the communities that rely on them.

While pricing decisions are ultimately business decisions, clear communication and alignment with user expectations are essential for preserving confidence in the platform. Constructive feedback like yours helps provide insight into how these changes are being received by real users and can contribute to future improvements.

It's unfortunate to hear that you've decided to discontinue using Copilot, but your perspective as an active user is important and deserves consideration. Hopefully, GitHub will continue listening to community feedback and explore ways to better balance product sustainability with accessibility for developers.

Thank you for sharing your experience and concerns with the community.

[nuttyproducer]

And where do you come from? What's your part in the process of Github copilot? You joined github 2 days ago?

[marioemanuelteodoru-stack]

I really, really hope the community gets together and does what it should do. A class action lawsuit. I paid $10 for what? For Haiku and sonet to butcher the code and give me error after error for 1 day? You took my money, I got to use it for 1 day in total, WITH EACH PROMPT PRODUCIND BAD, NON-FUNCTIONAL CODE. But who cares right? I should put some more money in, if I want some more bad code, right?