Skip to main content

​
Authentication

Clawdia supports OAuth and API keys for model providers. For Anthropic accounts, we recommend using an API key. Clawdia can also reuse Claude Code credentials, including 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 clawdia gateway).
  1. If the Gateway runs under systemd/launchd, prefer putting the key in ~/.clawdia/.env so the daemon can read it:
Then restart the daemon (or restart your Gateway process) and re-check:
If you’d rather not manage env vars yourself, the onboarding wizard can store API keys for daemon use: clawdia onboard. See Help for details on env inheritance (env.shellEnv, ~/.clawdia/.env, systemd/launchd).

​
Anthropic: Claude Code CLI setup-token (supported)

For Anthropic, the recommended path is an API key. If you’re already using Claude Code CLI, the setup-token flow is also supported. Run it on the gateway host:
Then verify and sync into Clawdia:
This should create (or refresh) an auth profile like anthropic:claude-cli in the agent auth store. Clawdia config sets auth.profiles["anthropic:claude-cli"].mode to "oauth" so the profile accepts both OAuth and setup-token credentials. Older configs that used "token" are auto-migrated on load. If you see an Anthropic error like:
…use an Anthropic API key instead. Alternative: run the wrapper (also updates Clawdia config):
Manual token entry (any provider; writes auth-profiles.json + updates config):
Automation-friendly check (exit 1 when expired/missing, 2 when expiring):
Optional ops scripts (systemd/Termux) are documented here: /automation/auth-monitoring clawdia models status loads Claude Code credentials into Clawdia’s auth-profiles.json and shows expiry (warns within 24h by default). clawdia doctor also performs the sync when it runs.
claude setup-token requires an interactive TTY.

​
Checking model auth status

​
Controlling which credential is used

​
Per-session (chat command)

Use /model <alias-or-id>@<profileId> to pin a specific provider credential for the current session (example profile ids: anthropic:claude-cli, anthropic:default). 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)

Set an explicit auth profile order override for an agent (stored in that agent’s auth-profiles.json):
Use --agent <id> to target a specific agent; omit it to use the configured default agent.

​
How sync works

  1. Claude Code stores credentials in ~/.claude/.credentials.json (or Keychain on macOS).
  2. Clawdia syncs those into ~/.clawdia/agents/<agentId>/agent/auth-profiles.json when the auth store is loaded.
  3. Refreshable OAuth profiles can be refreshed automatically on use. Static token profiles (including Claude Code CLI setup-token) are not refreshable by Clawdia.

​
Troubleshooting

​
“No credentials found”

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

​
Token expiring/expired

Run clawdia models status to confirm which profile is expiring. If the profile is anthropic:claude-cli, rerun claude setup-token.

​
Requirements

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