You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Framing: how work splits between subscriptions and API credits #6959
Resolved in an interview with the operator (2026-10-10):
Credits fund API-only work: Managed Agents, Batches, Messages API tools, and our own Agent SDK or claude -p runs with a linked-org API key. Subscriptions run Claude Code lanes, routines, cloud sessions and claude-code-action.
Credits come first when the two goals compete, because they expire each billing cycle.
Subscriptions are one account per workload. Each account runs to its limit and then waits for the reset. Lanes never rotate between subscription accounts automatically. Usage is read with the official claude -p "/usage".
Interactive sessions switch accounts by hand, soonest reset first, skipping accounts whose usage is already high.
Lanes are never blocked: a lane that hits its limit falls back to API keys, rotating through the linked orgs. API-key access is the route the terms sanction for automation.
Unused credits back critical lanes first. Whatever is still left expires, and the shortfall is tracked.
Activity
kyle-sexton commentedon Oct 11, 2026
Resolved in an interview with the operator (2026-10-10):
claude -pruns with a linked-org API key. Subscriptions run Claude Code lanes, routines, cloud sessions and claude-code-action.claude -p "/usage".claude -p(Should critical CI lanes run their own claude -p step instead of claude-code-action? #6967).github-actions commentedon Oct 11, 2026
Thanks for the report. Automated triage handed this issue to a maintainer.
Automated triage. A maintainer reviews it.