The Annual Subscriber "PRU Trap" and the limits of Copilot Max for agent workflows

[masstransferase]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot in GitHub

Body

I'm a massive fan of VS Code and Copilot’s UX, but the current consumption model is pushing my heavy agentic work to competitors.

The Core Issues:

1. The Annual "PRU Trap": As an annual subscriber, I am stuck on the legacy PRU system. With the recent adjustments, my Opus-class workhorse carries a 27x multiplier. A single multi-step agent session now drains a massive share of my allowance instantly.

2. Meter Anxiety: Even if I switch to the new monthly Copilot Max tier, hard-capped AI Credits are hostile to autonomous agent loops. Power users can easily burn through a $200 credit cap in days on Opus.

3. The Competitor Edge: Flat-rate or pooled-usage competitors (like Claude Code or Cursor) let me run long, multi-file agent sessions without watching a declining balance.

What would bring my heavy workloads back:

1. Fix the Annual Trap: Automatically migrate annual users to the new token-based AI Credit system with context caching, or waive the 27x PRU multipliers.

2. Predictable Power-User Runways: Offer a rate-limited, uncapped tier or significantly raise the credit ceiling for Copilot Max. Background agent loops shouldn't bill like dozens of independent premium chat interactions.

3. Prove the Value: Publish benchmarks on cost-to-finish and completion rates. If Copilot costs more than native API/competitor usage, show us the ROI in context efficiency.

The product quality is excellent, but the billing model actively penalizes the exact agent-heavy usage Copilot is built for. Predictable pricing would bring my primary workloads back immediately.

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