[Bugs] Title: App confuses GitHub accounts when checking Copilot quota (incorrectly ...

[guillaumelamb]

Mood: 😔
Category: Bugs

Title: App confuses GitHub accounts when checking Copilot quota (incorrectly blocks usage)

Summary:
The GitHub Copilot app displays an error stating that the credit/quota is exhausted, blocking all prompts. However, the active account still has available quota (roughly 23% of the monthly limit used). The error message appears to actually reflect the status of a second, linked GitHub account on the same machine, whose Copilot license has been deactivated.

Expected behavior:

• The app should check and display the quota for the active/selected account, not for another linked account on the same environment.
  Observed behavior:

• Account A (active): Copilot Business active, ~23% of monthly quota used, quota available → should work normally.
  The app still blocks prompts with a "quota exhausted" error, which appears to correspond to Account B's status (deactivated license).

Impact:
Complete inability to use Copilot, even though the active account has sufficient available quota.

Steps to reproduce:

1. Be signed in with two GitHub accounts on the same machine/app (one with a deactivated Copilot license).
2. Use Copilot with the active account that has available quota.
3. Observe that the app returns a "quota exhausted" error that doesn't match the actually active account.

Suggested priority: High (fully blocks product usage in multi-account setups).

---

Field	Value
App version	1.0.16
OS	Windows 10.0.26200
Theme	GitHub
Path	/chat
Tenure	Week 7

[Davsterl]

Hello,
Can you check on the account that's associated with that project in settings. It may be your deactivated account. The account that's specified under the project itself is the one that is used to talk to Copilot.
If not, please let me know!

[aymenfurter]

This should have been fixed very recently in the recent v1.0.16 release. Could you please check whether it still occurs in the latest version? (See: #1500)

[guillaumelamb]

Hi,
Thanks for the quick reply. I checked the project settings and the account associated with the project is indeed the correct one (the one with available Copilot quota) — not the deactivated account.
Despite this, I'm still getting the "quota exhausted" error and cannot prompt.
I'm using version 1.0.16.
Let me know if there's any additional info I can provide to help debug this.

[guillaumelamb]

@Davsterl here are the captures

[guillaumelamb]

Hi @Davsterl and @aymenfurter,
Still reproducible on the latest version (1.0.17). I double-checked the account configured for this project under Settings — it's correctly set to the account with available quota (GitHub's website confirms ~28% of the monthly limit used). However, the app's account switcher shows that same account at "AI credits used: 100%", and usage gets blocked with "Monthly AI credits exhausted" / "Usage blocked: organization has exceeded its Copilot budget" — matching the other (deactivated) account's status instead.
This makes the app unusable for me right now, so I've had to fall back to Copilot in VS Code as a workaround, which doesn't show this mismatch.
Happy to share more details or screenshots if that helps track it down.

[jokeyrhyme]

still having this issue in 1.0.25

[titan-ron]

Related, and I think this is the same root cause rather than only a lookup bug: the app binds one account per project, and that single binding serves both repo access and Copilot usage/quota. So the quota shown (and enforced) can't be independently pointed at the account whose license you actually want to spend — which is why setting the project's account correctly still doesn't resolve it here.

I've written up a proposal to split those into two independent settings ("repo identity" vs "AI identity"), with quota/credits and error messages read from the AI identity and the account named in the message: #1726 (comment)

Notably the runtime already isolates GitHub auth per session — github/copilot-sdk's public E2E suite (nodejs/test/e2e/per_session_auth.e2e.test.ts) runs two concurrent sessions under different tokens with different plans (individual_pro vs business) and asserts each resolves its own login/plan, and account.getQuota({ gitHubToken }) resolves quota per token. So the per-token plumbing exists; the app just doesn't expose it per project.

Same family: #1726, #1753, and #149 (closed, but with unresolved follow-ups asking for exactly this separation).

[mamoreau-devolutions]

+1 for fixing this, I use two GitHub Copilot accounts regularly, one of which has 100X more credits than the first one. The quota warnings pop in any session regardless of which quota applies. This makes them quite annoying but unfortunately also very much useless as they cannot be trusted. https://bsky.app/profile/awakecoding.com/post/3msl4nfzk6c27