Authentication
このコンテンツはまだ日本語訳がありません。
Kurahi supports OAuth and API keys for model providers. Each provider supports
the authentication methods listed on its provider page. For Anthropic: an API
key, or the long‑lived token created by claude setup-token.
See /concepts/oauth for the full OAuth flow and storage layout.
Anthropic: API key
Section titled “Anthropic: 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
kurahi gateway).
export ANTHROPIC_API_KEY="..."kurahi models status- If the Gateway runs under systemd/launchd, prefer putting the key in
~/.kolo/.envso the daemon can read it:
cat >> ~/.kolo/.env <<'EOF'ANTHROPIC_API_KEY=...EOFThen restart the daemon (or restart your Gateway process) and re-check:
kurahi models statuskurahi doctorIf you’d rather not manage env vars yourself, the onboarding wizard can store
API keys for daemon use: kurahi onboard.
See Help for details on env inheritance (env.shellEnv,
~/.kolo/.env, systemd/launchd).
Anthropic: setup-token (subscription auth)
Section titled “Anthropic: setup-token (subscription auth)”If you use a Claude subscription, run the setup-token flow on the gateway host:
claude setup-tokenThen paste it into Kurahi:
kurahi models auth setup-token --provider anthropicIf the token was created on another machine, paste it manually:
kurahi 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):
kurahi models auth paste-token --provider anthropickurahi models auth paste-token --provider openrouterAutomation-friendly check (exit 1 when expired/missing, 2 when expiring):
kurahi 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”kurahi models statuskurahi doctorControlling 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):
kurahi models auth order get --provider anthropickurahi models auth order set --provider anthropic anthropic:defaultkurahi 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:
kurahi models statusToken expiring/expired
Section titled “Token expiring/expired”Run kurahi 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)