GitHub Copilot Pro+ Agent blocked despite available Additional Usage budget (Support Ticket #4556631)

[JKPH00]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Copilot in GitHub

Body

Hello everyone,

I'm hoping someone from GitHub or the community can help me understand what is happening.

I am a GitHub Copilot Pro+ subscriber using Visual Studio Code on Windows 11.

I am actively developing a large educational software project called the Harper Builder Engine, and my development has now been blocked for two days.

Here is my situation:

Copilot Pro+ subscription is active.
I purchased directly from GitHub.
Included AI credits (7,000) have been exhausted.
Additional Usage is enabled.
My Additional Usage budget is set to $200.
My current Additional Usage is only about $61.41.

However, GitHub Copilot Agent in VS Code immediately refuses to execute any task and reports:

"You've reached your additional usage limit for your plan."

If I click "Pay to continue," GitHub redirects me to a page asking me to upgrade to Copilot Max instead of continuing to bill against my configured Additional Usage budget.

I have already opened GitHub Support ticket #4556631, but I have not yet received a response, and I am now entering my second day of lost development time.

My question is simply this:

Is this expected behavior for Copilot Pro+, or does it indicate a billing/account synchronization problem?

If anyone from GitHub sees this, I would greatly appreciate having ticket #4556631 reviewed or escalated.

I am not looking for free service or a workaround—I simply need to understand why my configured Additional Usage budget is not allowing Copilot Agent to continue working.

Thank you very much for any guidance.

[geojose911]

Hey
I dug into this a bit, and I think I can explain what's probably going on, though it's honestly a frustrating one, this isn't a bug in your account specifically ,it's how the new usage-based system is designed to work, even though it's confusing and doesn't match what you'd expect from your $200 budget.

Once you've used your included credits, you can keep going by spending against your Additional Usage budget, but for individual plans, GitHub can cap your total additional usage based on things like your usage pattern, billing history, or account verification status. And once you hit that cap, the product doesn't let you keep paying against your own budget, it just pushes you to upgrade to Copilot Max instead.

Which is exactly what you're describing. You set a $200 budget in good faith, you're only $61 into it, and yet you're getting blocked and pointed at an upgrade page instead. So there really are two separate limits here, the one you configured, and a second one GitHub applies quietly on top of it that has nothing to do with the number you picked. That second one is what's actually stopping you

This isn't just you. It lines up with a change GitHub rolled out on June 1, 2026 when they moved Copilot to usage-based billing. Buried in their changelog for that update is a line that basically says: once you use up your included credits, you can keep going by spending against your Additional Usage budget, but for individual plans, GitHub reserves the right to cap your total additional usage based on stuff like your usage pattern, billing history, or how verified your account is

One more thing that might actually help when you follow up on your ticket, mention that June 1 changelog post by name. That's honestly the strongest card you've got here, because right now it probably just reads to support as "user's confused about their own budget," when really it's "GitHub's own documentation admits there's a second cap." Naming it changes the conversation.

I'd also just flat out ask them which one of the three things is it usage pattern, billing history, or verification that's capping me?
Because nowhere in the product does it tell you that, and you shouldn't have to guess.

And honestly, given how many people are posting the same story right now, I wouldn't be shy about asking for this to get bumped to whoever actually owns Copilot billing instead of sitting in general support queue. Doesn't hurt to ask.

Anyway, hope this gets sorted for you soon ,losing two days mid-project because of a billing quirk is genuinely rough, especially on something you're actively building.

[JKPH00]

Warmest thanks for your response. That explanation fits my experience much better than the information currently shown in GitHub's billing pages. If there is indeed an internal account cap separate from the user-configured Additional Usage budget, I hope GitHub will document it and expose it in the UI. Right now the interface strongly implies that my configured $200 budget is the operative limit, which led me to believe something was wrong with my account. I appreciate you taking the time to explain it. I can't afford the down time. I'm going to be looking for another way where I can get the work done someplace else.

…

-------- Original Message --------

On Monday, 07/13/26 at 10:39 Geo ***@***.***> wrote: Hey I dug into this a bit, and I think I can explain what's probably going on, though it's honestly a frustrating one, this isn't a bug in your account specifically ,it's how the new usage-based system is designed to work, even though it's confusing and doesn't match what you'd expect from your $200 budget. Once you've used your included credits, you can keep going by spending against your Additional Usage budget, but for individual plans, GitHub can cap your total additional usage based on things like your usage pattern, billing history, or account verification status. And once you hit that cap, the product doesn't let you keep paying against your own budget, it just pushes you to upgrade to Copilot Max instead. Which is exactly what you're describing. You set a $200 budget in good faith, you're only $61 into it, and yet you're getting blocked and pointed at an upgrade page instead. So there really are two separate limits here, the one you configured, and a second one GitHub applies quietly on top of it that has nothing to do with the number you picked. That second one is what's actually stopping you And you're not the only person this has happened to, a handful of others have posted about the exact same thing since the change went live — Reply to this email directly, [view it on GitHub](#201798?email_source=notifications&email_token=BAFYTBBLNZ37MISCBKVOZDL5ETYA3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGIZTMOJSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17623692), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BAFYTBGPPRBYU3JYXZ34I235ETYA3AVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBUGIYDKNBWUF3AE). Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for [iOS](https://github.com/notifications/mobile/ios/BAFYTBAQQAE7CTBAXYHJM2L5ETYA3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGIZTMOJSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM) and [Android](https://github.com/notifications/mobile/android/BAFYTBDNL4BVC2OL6TMV56D5ETYA3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGIZTMOJSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE). Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[Mr-Nilarnab]

@JKPH00

Based on your description, the most confusing part isn't that the Agent stopped working—it's that the UI appears to communicate one limit while enforcing another.

If your configured Additional Usage budget is $200 but you're blocked after approximately $61 in usage, the product should clearly indicate whether:

• an account-specific spending cap has been reached,
• a billing synchronization issue has occurred,
• or the requested Copilot feature isn't eligible for Additional Usage under your current plan.

Redirecting users to upgrade to Copilot Max without explaining why their existing Additional Usage budget can't be used makes it difficult to determine whether the behavior is expected or the result of an account issue.

I hope Support can clarify whether this is intended behavior or a billing synchronization problem. Regardless of the outcome, improving the error message to explain the exact reason for the block would save users a great deal of confusion and unnecessary downtime.