GitHub Copilot Pro keeps losing value: stricter limits, missing model access, and pressure toward Pro+

[artidones]

Discussion Type

Product Feedback

Discussion Content

I would like to share some honest feedback and frustration about the current direction of GitHub Copilot Pro.

I have been a Copilot user for more than a year, and one of the biggest reasons I adopted it early was because it felt simple, reliable, and worth the price. In the beginning, the Pro plan felt much more straightforward. There were no constant concerns about request caps, hidden restrictions, reduced usage, or being pushed toward a more expensive tier just to maintain a good experience.

Now, however, it feels like the value of the $10 Pro plan is being reduced more and more over time.

My main concerns are:

The Pro plan does not include access to Opus 4.7
For many users, model access is one of the most important parts of the product. When a premium model is not available in Pro, it creates the impression that the plan is intentionally being kept limited, even for long-time paying customers.
Microsoft appears to be increasingly restricting usage on Pro
What used to feel like a productive tool now feels heavily controlled. The experience no longer feels like “pay once and use normally.” Instead, it feels like users are constantly being managed through limits.
There were no request limits like this in the beginning
One of the reasons many of us subscribed early was because Copilot originally felt open and practical for real daily development. Over time, limits started appearing, and now those limits seem to be getting tighter. That creates a very bad feeling for users who have supported the product since earlier stages.
The Pro plan seems intentionally weakened to push users into Pro+
This is probably the biggest issue from a customer trust perspective. When a lower paid tier keeps losing features, losing flexibility, and gaining more restrictions, it starts to feel less like product improvement and more like forced upselling. Instead of making Pro+ attractive by adding clear extra value, it feels like Pro is being made worse so users feel pressured to upgrade.
Long-time subscribers are being treated like entry-level users
People who have been paying for over a year should not feel like the service they originally signed up for is slowly being downgraded. Loyalty should matter. At the very least, existing paying users should not feel like they are constantly losing value.

My point is not that GitHub or Microsoft should never create higher tiers. That is normal. The problem is how this is being done. There is a big difference between:

creating a better premium tier with genuinely new benefits, and
reducing the usefulness of the existing paid plan until users feel forced to move up.

Right now, Copilot Pro feels much closer to the second case.

If GitHub wants users to trust Copilot long term, then the company should be much more transparent about:

which models are included in each plan,
what the actual usage limits are,
how those limits changed over time,
and why the Pro plan keeps feeling more restricted than it used to.

From a customer perspective, the current strategy gives the impression that the original Pro plan is being squeezed as much as possible in order to maximize upgrades to Pro+.

That is disappointing, especially for users like me who have been paying for Copilot for a long time and remember when the product felt much less restricted and much more useful at the same price point.

I hope GitHub seriously reconsiders this direction, because right now Copilot Pro no longer feels like the fair, developer-friendly plan it once seemed to be.

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

[Santiagorich]

It's pressure towards enterprise if anything, in pro+ I have the same issues

I literally can't use anything but auto (which defaults to a really dumbed down version of chatgpt 5.4), if I try any other model i'm rate limited,

I'm at 13% of my monthly premium requests "allowance" by the way

[pdparchitect]

We are already on Pro+ (paid in full for the year) plus thousands of $ in inference costs and I guess this is still not enough.

[merigens63]

You’ve summarized the core frustration really well especially the feeling that value is being gradually reduced instead of clearly expanded between tiers. That kind of slow restriction really affects trust, even if the feature set is technically “improving” on higher plans. It’s similar to how in any eCommerce fulfillment solution, changing rules mid-flow without clear communication can break user confidence fast, even if the system is still working technically.