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

未关闭
  • 哪里不对？
#2,873 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
43/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, node.js
领域
api, backend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Java
星标
10.7k
派生
1.5k
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

github/copilot-sdk 的其他 Issue

查看 github/copilot-sdk 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。