## GitHub Copilot Pro: Budget Field Greyed Out & Premium Requests Always Zero #172568
Replies: 3 comments
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Hi @PPGOli Thanks for sharing such a detailed report — that helps a lot 🙏 At the moment, Copilot Pro personal accounts don’t support setting a custom budget or enabling additional premium requests. The field appearing greyed out and resetting to zero is expected behavior until GitHub rolls out expanded options for personal plans. There isn’t a confirmed workaround right now, but I’d recommend keeping an eye on: If your workflow depends on higher request capacity, one option is to reach out directly to GitHub Support so they can confirm your account status and share any updates on timelines. Hopefully GitHub will provide more clarity soon on when personal accounts can adjust premium requests. |
Beta Was this translation helpful? Give feedback.
-
This reply is ridiculous because after creating the account in July I was
able to create a (10 USD) budget and I could use it.
I only disabled the function at the beginning of this month because Gtihub
started sending me contradicting messages about the status of the premium
requests.
And even the popup banner in the chat and elsewhere was suggesting the
option to "update the budget settings".
Anyway, I am cancelling my subscription at this moment because this reply
is not what I expected.
Best Regards
Oliver Ohlendorf
…On Sun, 7 Sept 2025, 02:25 Victor Moni, ***@***.***> wrote:
Hi @PPGOli <https://github.com/PPGOli>
Thanks for sharing such a detailed report — that helps a lot 🙏
At the moment, Copilot Pro personal accounts don’t support setting a
custom budget or enabling additional premium requests. The field appearing
greyed out and resetting to zero is expected behavior until GitHub rolls
out expanded options for personal plans.
There isn’t a confirmed workaround right now, but I’d recommend keeping an
eye on:
👉 GitHub Copilot Changelog <https://github.blog/changelog/label/copilot/>
If your workflow depends on higher request capacity, one option is to
reach out directly to GitHub Support <https://support.github.com/contact>
so they can confirm your account status and share any updates on timelines.
Hopefully GitHub will provide more clarity soon on when personal accounts
can adjust premium requests.
—
Reply to this email directly, view it on GitHub
<#172568 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT5G6EO2KFOHGDL55ZM7YND3RN3QDAVCNFSM6AAAAACFZM2ZN2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZSHE2DCMI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Copilot Feature Area
General
Body
Summary:
I’m using GitHub Copilot Pro with a personal account. I’ve noticed that the budget field for premium requests is always greyed out, and any attempt to set a budget or enable additional premium requests fails—the field resets to zero and does not save. This persists regardless of browser, cookies, or cache.
Steps I’ve Taken:
Observed Behavior:
Questions:
Impact:
This limitation is affecting my workflow and planning, as I cannot anticipate or pay for extra premium requests.
References:
Would appreciate any official update or workaround!
Beta Was this translation helpful? Give feedback.
All reactions