SDK-backed sessions in VS Code report credit limit reached while standalone CLI works

Aperta
  • Qualcosa non va?
#2,873 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
43/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, node.js
Ambito
api, backend

Direzione di ricerca

Start by tracing how CopilotClient launches the bundled runtime and passes the authenticated account context; the report does not name source files or tests. Compare the SDK-backed flow with the working standalone CLI path, then identify which credit limit produces the error. Done means the flow works when credits remain, or the error identifies the separate blocking limit.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Copilot sessions using VS Code’s bundled  @github/copilot-sdk  report that I’ve reached my credit limit, while standalone Copilot CLI and VS Code local mode still work with the same account.

Related VS Code report, including screenshots: https://github.com/microsoft/vscode/issues/344615

I’m reporting this here because the failing flow uses the SDK. I haven’t reproduced it in a standalone SDK application, so I don’t know whether the cause is in the SDK, VS Code’s integration, or backend credit enforcement.

Error: You've reached your credit limit. To continue working, please contact your organization's Copilot admin or wait until your credits reset on October 31, 2026 at 8:00 PM.

At the same time, the usage display shows 13,868.6 / 24,000 credits used on Copilot Business, with the same reset time.

Environment

• Plan: Copilot Business
• OS: Windows 11 x64 (10.0.26100)
• VS Code: 1.143.1
• Copilot Chat extension:  GitHub.copilot-chat  0.71.0
• Bundled SDK:  @github/copilot-sdk  1.0.23-preview.5
• Native runtime package:  @github/copilot-sdk-win32-x64  1.0.23-preview.5
• SDK host: embedded Node.js 24.21.0 / Electron 43.7.7
• Standalone Copilot CLI: 1.0.104
• Observed: October 27, 2026, EDT (UTC-04:00)

Steps to reproduce in the affected environment

  1. Sign in to VS Code with the account that has Copilot Business access.
  2. Confirm that the usage display shows remaining credits.
  3. Send a prompt through the SDK-backed Copilot agent flow.
  4. Observe the credit-limit error.
  5. Send a prompt through standalone Copilot CLI using the same account. It succeeds.
  6. Test VS Code local mode. It also succeeds.

SDK integration details

The VS Code agent-host log confirms that it starts  CopilotClient  and uses the bundled runtime:

[Copilot] Starting CopilotClient...
[Copilot] Set CLI env: GITHUB_COPILOT_INTEGRATION_ID=vscode-chat
[Copilot] Using bundled runtime path: ...@github\copilot-sdk-win32-x64\prebuilds\win32-x64\copilot-runtime.exe
[Copilot] CopilotClient started successfully

Expected behavior

The SDK-backed flow should work while the applicable credit allocation has capacity. If a separate budget blocks this flow, the error should identify that limit so it can be reconciled with the usage display.

Lingua principale
Java
Stelle
10.7k
Fork
1.5k
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/copilot-sdk

Tutte le issue di github/copilot-sdk

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.