Authentication
このコンテンツはまだ日本語訳がありません。
Authentication
Section titled “Authentication”CoderClaw supports OAuth and API keys for model providers. For Anthropic
accounts, we recommend using an API key. For Claude subscription access,
use the long‑lived token created by claude setup-token.
See /concepts/oauth for the full OAuth flow and storage layout.
Recommended Anthropic setup (API key)
Section titled “Recommended Anthropic setup (API key)”If you’re using Anthropic directly, use an API key.
- Create an API key in the Anthropic Console.
- Put it on the gateway host (the machine running
coderclaw gateway).
export ANTHROPIC_API_KEY="..."coderclaw models status- If the Gateway runs under systemd/launchd, prefer putting the key in
~/.coderclaw/.envso the daemon can read it:
cat >> ~/.coderclaw/.env <<'EOF'ANTHROPIC_API_KEY=...EOFThen restart the daemon (or restart your Gateway process) and re-check:
coderclaw models statuscoderclaw doctorIf you’d rather not manage env vars yourself, the onboarding wizard can store
API keys for daemon use: coderclaw onboard.
See Help for details on env inheritance (env.shellEnv,
~/.coderclaw/.env, systemd/launchd).
Anthropic: setup-token (subscription auth)
Section titled “Anthropic: setup-token (subscription auth)”For Anthropic, the recommended path is an API key. If you’re using a Claude subscription, the setup-token flow is also supported. Run it on the gateway host:
claude setup-tokenThen paste it into CoderClaw:
coderclaw models auth setup-token --provider anthropicIf the token was created on another machine, paste it manually:
coderclaw models auth paste-token --provider anthropicIf you see an Anthropic error like:
This credential is only authorized for use with Claude Code and cannot be used for other API requests.…use an Anthropic API key instead.
Manual token entry (any provider; writes auth-profiles.json + updates config):
coderclaw models auth paste-token --provider anthropiccoderclaw models auth paste-token --provider openrouterAutomation-friendly check (exit 1 when expired/missing, 2 when expiring):
coderclaw models status --checkOptional ops scripts (systemd/Termux) are documented here: /automation/auth-monitoring
claude setup-tokenrequires an interactive TTY.
Checking model auth status
Section titled “Checking model auth status”coderclaw models statuscoderclaw doctorAPI key rotation behavior (gateway)
Section titled “API key rotation behavior (gateway)”Some providers support retrying a request with alternative keys when an API call hits a provider rate limit.
- Priority order:
CODERCLAW_LIVE_<PROVIDER>_KEY(single override)<PROVIDER>_API_KEYS<PROVIDER>_API_KEY<PROVIDER>_API_KEY_*
- Google providers also include
GOOGLE_API_KEYas an additional fallback. - The same key list is deduplicated before use.
- CoderClaw retries with the next key only for rate-limit errors (for example
429,rate_limit,quota,resource exhausted). - Non-rate-limit errors are not retried with alternate keys.
- If all keys fail, the final error from the last attempt is returned.
Controlling which credential is used
Section titled “Controlling which credential is used”Per-session (chat command)
Section titled “Per-session (chat command)”Use /model <alias-or-id>@<profileId> to pin a specific provider credential for the current session (example profile ids: anthropic:default, anthropic:work).
Use /model (or /model list) for a compact picker; use /model status for the full view (candidates + next auth profile, plus provider endpoint details when configured).
Per-agent (CLI override)
Section titled “Per-agent (CLI override)”Set an explicit auth profile order override for an agent (stored in that agent’s auth-profiles.json):
coderclaw models auth order get --provider anthropiccoderclaw models auth order set --provider anthropic anthropic:defaultcoderclaw models auth order clear --provider anthropicUse --agent <id> to target a specific agent; omit it to use the configured default agent.
Troubleshooting
Section titled “Troubleshooting”“No credentials found”
Section titled ““No credentials found””If the Anthropic token profile is missing, run claude setup-token on the
gateway host, then re-check:
coderclaw models statusToken expiring/expired
Section titled “Token expiring/expired”Run coderclaw models status to confirm which profile is expiring. If the profile
is missing, rerun claude setup-token and paste the token again.
Requirements
Section titled “Requirements”- Claude Max or Pro subscription (for
claude setup-token) - Claude Code CLI installed (
claudecommand available)