Clarify quota/billing behavior for Claude Agent SDK runtime
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- typescript
Línea de trabajo
Start with the README, package.json, src/lib/claude-client.ts, and src/lib/runtime/sdk-runtime.ts to trace which runtime and authentication paths the issue describes. Verify the quota behavior against the linked Anthropic documentation, then clarify the supported billing sources in the README and runtime selection UI; done means users can tell which account or quota their chosen runtime uses.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hi, thanks for building CodePilot. I am evaluating the runtime and remote bridge behavior, and noticed one billing/quota detail that may be worth documenting more explicitly.
CodePilot appears to support a Claude Code / Claude Agent SDK runtime via @anthropic-ai/claude-agent-sdk, while the README also says users can configure providers and track token usage/costs. Anthropic's current docs say that, starting June 15, 2026, Claude Agent SDK and claude -p usage on Claude subscription plans will draw from a separate monthly Agent SDK credit. API key users continue with normal pay-as-you-go API billing.
Relevant docs:
- https://code.claude.com/docs/en/agent-sdk/overview
- https://support.claude.com/en/articles/15036540-use-the-claude-agent-sdk-with-your-claude-plan
CodePilot references I checked:
package.jsondepends on@anthropic-ai/claude-agent-sdksrc/lib/claude-client.tsimportsqueryfrom@anthropic-ai/claude-agent-sdksrc/lib/runtime/sdk-runtime.tsexposes theclaude-code-sdkruntime- README says Claude Code CLI is optional for basic chat and mentions token/cost tracking
Questions:
- When using the Claude Agent SDK runtime with Claude subscription auth, does usage count against the separate Agent SDK monthly credit?
- When CodePilot injects a configured provider API key/base URL into the SDK subprocess, does usage count against that provider/API billing instead?
- Are remote Bridge sessions, such as Feishu/Telegram/Discord turns, counted the same way as local chat when they use the SDK runtime?
- Could the UI or README show the current runtime's quota source, for example:
- Native provider runtime -> configured provider/API key billing
- Claude Agent SDK via Claude subscription -> Agent SDK monthly credit
- Claude Agent SDK via API key/provider -> API/provider billing
- Local interactive Claude Code/channel-style runtime, if supported -> different from Agent SDK /
claude -p
Product-level concern:
A user may try CodePilot expecting their existing Claude Max subscription to provide a broad remote Claude Code experience across Feishu/Telegram/Discord/etc. But if the advanced or remote workflow depends mainly on the Claude Agent SDK runtime, that experience may be constrained by a separate Agent SDK credit and may require additional usage credits or API billing after that credit is exhausted.
That could materially affect user expectations, adoption, and retention. Users might assume all CodePilot usage is billed through the configured provider or through normal Claude Code interactive limits, while Agent SDK usage may draw from a different quota/billing source.
It may be helpful to clarify this in the README and runtime selection UI, and possibly add a small warning/label showing which account/quota/billing source the current runtime will consume.
Apologies if I misunderstood part of the runtime routing. I am filing this mainly as a docs/UX clarification because the quota source seems important for users evaluating the product.
- Lenguaje dominante
- TypeScript
- Estrellas
- 6.5k
- Forks
- 697
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de op7418/CodePilot
-
发生错误时提醒Error:successAbiertobug P0-crash-or-interrupt
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Effort selector dropdown hidden for GLM models — blocks access to GLM-5.2 High/Max effort tiersAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
bug P0-crash-or-interrupt
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Todos los issues de op7418/CodePilot
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
backnotprop/plannotator#2914 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
microsoft/vscode-containers#655 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
dsh-tauri-desk/deepseek-harness-desktop#1477 · 1 comentario ·