Proposal: Flexible Burst Capacity for Heavy Copilot Workflows

[teddyeshafer-creator]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot in GitHub

Body

I’d like to propose a “Burst Capacity” system for GitHub Copilot power users and heavy development workflows.

Right now, Copilot plans appear to combine:
• monthly usage/budget systems,
• weekly throughput limits,
• and session throttling.

The issue is that these systems feel disconnected from one another from the developer’s perspective.

This creates a frustrating experience where users may still have available monthly budget or premium usage remaining, but are still heavily constrained by weekly limits during concentrated development periods.

Modern software development is often bursty by nature:
• architecture sessions,
• refactors,
• debugging marathons,
• release preparation,
• migrations,
• and long agentic coding workflows.

Many professional developers may use relatively little AI compute for several days, then consume heavily during focused sprint sessions.

Proposal:
Introduce an optional “Burst Capacity” system tied to plan scaling or additional budget allocation.

Flexible Burst Scaling:
If a user:
• increases spend,
• buys extra credits,
• or upgrades temporarily,

then:
• weekly throughput ceilings increase proportionally for that billing period or rolling window.

This would better align Copilot with real-world development workflows while still preserving GitHub’s ability to manage infrastructure stability and compute costs.

Importantly, this proposal is not asking for unlimited usage.

It is asking for:
• better elasticity,
• better alignment between budget and throughput,
• and a more transparent scaling model for legitimate heavy-use workflows.

I believe this would significantly improve the experience for serious Copilot users while also creating a more intuitive relationship between pricing, compute usage, and practical development capacity.

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

[Kutasy]

Ok