Clarify quota/billing behavior for Claude Agent SDK runtime

Aperta
  • Qualcosa non va?
#624 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
48/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript
Ambito
developer-experience, documentation

Direzione di ricerca

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.

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

Descrizione

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:

CodePilot references I checked:

  • package.json depends on @anthropic-ai/claude-agent-sdk
  • src/lib/claude-client.ts imports query from @anthropic-ai/claude-agent-sdk
  • src/lib/runtime/sdk-runtime.ts exposes the claude-code-sdk runtime
  • README says Claude Code CLI is optional for basic chat and mentions token/cost tracking

Questions:

  1. When using the Claude Agent SDK runtime with Claude subscription auth, does usage count against the separate Agent SDK monthly credit?
  2. When CodePilot injects a configured provider API key/base URL into the SDK subprocess, does usage count against that provider/API billing instead?
  3. Are remote Bridge sessions, such as Feishu/Telegram/Discord turns, counted the same way as local chat when they use the SDK runtime?
  4. 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.

Lingua principale
TypeScript
Stelle
6.5k
Fork
697
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

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 op7418/CodePilot

Tutte le issue di op7418/CodePilot

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.