After enabling AI security scanning, I noticed a substantial amount of my Copilot credits were consumed. What was particularly frustrating was that I was not aware this feature would draw from my Copilot credit allocation, and I was unable to find clear documentation explaining that behavior beforehand. As a result, I exhausted my available credits much sooner than expected without receiving value that I felt justified the consumption.
The larger concern is what happened afterward. I have Bring Your Own Key (BYOK) configured and local models available in VS Code. However, once my Copilot credits were depleted, I was unable to use Copilot functionality at all. This raised questions about the subscription model. As a paying customer, it's unclear whether the monthly subscription fee grants access to the Copilot platform itself, access to a fixed pool of credits, or both. The current experience creates the impression that when credits are exhausted, access to the product is effectively disabled regardless of other available configurations.
In addition, I encountered what appears to be a bug related to account management after credits were exhausted. As a consultant, I regularly work across multiple GitHub Enterprise and GitHub Enterprise Cloud environments and frequently switch between accounts. Once my personal account ran out of credits, I was no longer able to switch profiles or change the preferred GitHub account used by the Copilot extension within VS Code.
Even after purchasing additional credits, the profile switching issue remained unresolved. This created a situation where I could neither effectively use my personal subscription nor transition to an enterprise-backed account that still had available entitlement.
Overall, the combination of unexpected credit consumption, unclear product behavior when credits run out, and account-switching limitations has significantly reduced my confidence in the reliability and predictability of the GitHub Copilot experience. I hope GitHub can provide greater transparency around credit usage, clarify entitlement behavior, and address the account management issues for users who operate across multiple organizations and subscriptions.
Vscode Insiders
Version: 1.130.0-insider (Universal)
Commit: 5e21260
Date: 2026-07-17T16:24:39Z (2 days ago)
Electron: 42.6.0
ElectronBuildId: 14623276
Chromium: 148.0.7778.280
Node.js: 24.18.0
V8: 14.8.178.38-electron.0
OS: Darwin arm64 27.0.0
After enabling AI security scanning, I noticed a substantial amount of my Copilot credits were consumed. What was particularly frustrating was that I was not aware this feature would draw from my Copilot credit allocation, and I was unable to find clear documentation explaining that behavior beforehand. As a result, I exhausted my available credits much sooner than expected without receiving value that I felt justified the consumption.
The larger concern is what happened afterward. I have Bring Your Own Key (BYOK) configured and local models available in VS Code. However, once my Copilot credits were depleted, I was unable to use Copilot functionality at all. This raised questions about the subscription model. As a paying customer, it's unclear whether the monthly subscription fee grants access to the Copilot platform itself, access to a fixed pool of credits, or both. The current experience creates the impression that when credits are exhausted, access to the product is effectively disabled regardless of other available configurations.
In addition, I encountered what appears to be a bug related to account management after credits were exhausted. As a consultant, I regularly work across multiple GitHub Enterprise and GitHub Enterprise Cloud environments and frequently switch between accounts. Once my personal account ran out of credits, I was no longer able to switch profiles or change the preferred GitHub account used by the Copilot extension within VS Code.
Even after purchasing additional credits, the profile switching issue remained unresolved. This created a situation where I could neither effectively use my personal subscription nor transition to an enterprise-backed account that still had available entitlement.
Overall, the combination of unexpected credit consumption, unclear product behavior when credits run out, and account-switching limitations has significantly reduced my confidence in the reliability and predictability of the GitHub Copilot experience. I hope GitHub can provide greater transparency around credit usage, clarify entitlement behavior, and address the account management issues for users who operate across multiple organizations and subscriptions.
Vscode Insiders
Version: 1.130.0-insider (Universal)
Commit: 5e21260
Date: 2026-07-17T16:24:39Z (2 days ago)
Electron: 42.6.0
ElectronBuildId: 14623276
Chromium: 148.0.7778.280
Node.js: 24.18.0
V8: 14.8.178.38-electron.0
OS: Darwin arm64 27.0.0