Repository navigation
Probe: does a self-written claude -p step in GitHub Actions draw the linked org's API credits? #6962
Description
The credits article excludes runs started by the Claude Code GitHub Action, even with -p, but does not say whether a workflow that installs the CLI and runs claude -p with an org key is covered. Probe: note the org's credit balance, run one small claude -p step with that org's key, re-read the balance. Spends real credits, so it needs the operator's go. Also probe one claude plugin eval run the same way (#6405, #6649).
Decisions (owner, 2026-10-16)
- Credential choice. Claude Code picks one credential by presence and never falls back on its own (https://code.claude.com/docs/en/authentication#authentication-precedence). So every switch happens in the harness between runs, and the API key is present only in the fallback run's environment. An Action-run (claude-code-action) lane is never given a key: credits do not cover Action runs, and a set key would replace its subscription token.
- open: pick the credits-only org and the timing of the probe. This probe gates the CI fallback.
Activity
github-actions commentedon Oct 11, 2026
Thanks for the report. Automated triage handed this issue to a maintainer.
Automated triage. A maintainer reviews it.
kyle-sexton commentedon Oct 18, 2026
Result: yes, it draws the linked org's included API credits.
claude -p(CLI 2.1.302, claude-opus-5-5, 1 turn) with only the linked org's API key in its environment. No checkout and no claude-code-action.is_error: false,total_cost_usd: 0.0275.This matches support article 17154008:
claude -prun with an API key from the linked Console organization "is billed as Agent SDK usage", and the credits cover it. Runs started by the Claude Code GitHub Action remain uncovered.Next: the
claude-lanelauncher (key first, then the role's own subscription), with intake moving first. This unblocks #6967. Theclaude plugin evalhalf of this issue is not probed yet and stays with #6405/#6649.