Skip to content

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.

If you’re using Anthropic directly, use an API key.

  1. Create an API key in the Anthropic Console.
  2. Put it on the gateway host (the machine running kurahi gateway).
Terminal window
export ANTHROPIC_API_KEY="..."
kurahi models status
  1. If the Gateway runs under systemd/launchd, prefer putting the key in ~/.kolo/.env so the daemon can read it:
Terminal window
cat >> ~/.kolo/.env <<'EOF'
ANTHROPIC_API_KEY=...
EOF

Then restart the daemon (or restart your Gateway process) and re-check:

Terminal window
kurahi models status
kurahi doctor

If 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:

Terminal window
claude setup-token

Then paste it into Kurahi:

Terminal window
kurahi models auth setup-token --provider anthropic

If the token was created on another machine, paste it manually:

Terminal window
kurahi models auth paste-token --provider anthropic

If 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):

Terminal window
kurahi models auth paste-token --provider anthropic
kurahi models auth paste-token --provider openrouter

Automation-friendly check (exit 1 when expired/missing, 2 when expiring):

Terminal window
kurahi models status --check

Optional ops scripts (systemd/Termux) are documented here: /automation/auth-monitoring

claude setup-token requires an interactive TTY.

Terminal window
kurahi models status
kurahi doctor

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).

Set an explicit auth profile order override for an agent (stored in that agent’s auth-profiles.json):

Terminal window
kurahi models auth order get --provider anthropic
kurahi models auth order set --provider anthropic anthropic:default
kurahi models auth order clear --provider anthropic

Use --agent <id> to target a specific agent; omit it to use the configured default agent.

If the Anthropic token profile is missing, run claude setup-token on the gateway host, then re-check:

Terminal window
kurahi models status

Run kurahi models status to confirm which profile is expiring. If the profile is missing, rerun claude setup-token and paste the token again.

  • Claude Max or Pro subscription (for claude setup-token)
  • Claude Code CLI installed (claude command available)