Part of #6844.
Context
init --interactive's wizard currently offers device-flow OAuth (claude setup-token-style, tied to a personal Claude.ai/Claude Code subscription) as its first option for claude-cli, with a pasted-PAT fallback as option 2. ANTHROPIC_API_KEY already works as a credential (status.js:379) but is never offered by the wizard at all, and there's no equivalent audit for codex-cli's credential options.
Requirements
- Document, for both
claude-cli and codex-cli, every credential mechanism each CLI actually supports (OAuth/subscription-based session, a plain API key, any other mechanism), citing the real CLI behavior (not assumptions) -- run each CLI's own --help/auth docs and confirm empirically where practical.
- Write a clear recommendation: which credential type should be the default-recommended path for laptop/interactive use vs. unattended/fleet-mode (server, Docker, CI) use, and why -- covering the real trade-offs (a subscription-backed OAuth token uses plan-included usage but requires an interactive browser step and is tied to one human's account; an API key is server-friendly and scriptable but bills per-token via the provider's console, separate from any subscription).
- This is a design/recommendation deliverable -- do not change the wizard's actual behavior in this issue.
Deliverables
Expected Outcome
A clear, evidence-based default recommendation exists before the wizard itself is changed, so the implementation issue isn't guessing at what to prioritize.
Part of #6844.
Context
init --interactive's wizard currently offers device-flow OAuth (claude setup-token-style, tied to a personal Claude.ai/Claude Code subscription) as its first option forclaude-cli, with a pasted-PAT fallback as option 2.ANTHROPIC_API_KEYalready works as a credential (status.js:379) but is never offered by the wizard at all, and there's no equivalent audit forcodex-cli's credential options.Requirements
claude-cliandcodex-cli, every credential mechanism each CLI actually supports (OAuth/subscription-based session, a plain API key, any other mechanism), citing the real CLI behavior (not assumptions) -- run each CLI's own--help/auth docs and confirm empirically where practical.Deliverables
packages/loopover-miner/docs/or a design comment on this issue) covering both providers, informing epic: standardize AMS coding-agent credentials + close the token-usage observability gap (ORB parity) #6844's wizard-update sub-issue.Expected Outcome
A clear, evidence-based default recommendation exists before the wizard itself is changed, so the implementation issue isn't guessing at what to prioritize.