Fix checklist for No credentials found for profile anthropicdefault

Confirm where auth profiles live (new vs legacy paths)
Current: ~/.openclaw/agents/<agentId>/agent/auth-profiles.json
Legacy: ~/.openclaw/agent/* (migrated by openclaw doctor)
Confirm your env var is loaded by the Gateway
If you set ANTHROPIC_API_KEY in your shell but run the Gateway via systemd/launchd, it may not inherit it. Put it in ~/.openclaw/.env or enable env.shellEnv.
Make sure you’re editing the correct agent
Multi‑agent setups mean there can be multiple auth-profiles.json files.
Sanity‑check model/auth status
Use openclaw models status to see configured models and whether providers are authenticated.
Fix checklist for No credentials found for profile anthropic
This means the run is pinned to an Anthropic auth profile, but the Gateway can’t find it in its auth store.
Use a setup-token
Run claude setup-token, then paste it with openclaw models auth setup-token --provider anthropic.
If the token was created on another machine, use openclaw models auth paste-token --provider anthropic.
If you want to use an API key instead
Put ANTHROPIC_API_KEY in ~/.openclaw/.env on the gateway host.
Clear any pinned order that forces a missing profile:
openclaw models auth order clear --provider anthropic
Confirm you’re running commands on the gateway host
In remote mode, auth profiles live on the gateway machine, not your laptop.