Troubleshoot issues

[bitter spire]

I just asked my bot to switch my WhatsApp from pairing to allowlist type with my number to allow and then it did not restart again and came with this error:

[clawdbot] ⚠️ Agent failed before reply: No API key found for provider "anthropic". Auth store: /home/ubuntu/.clawdbot/agents/main/agent/auth-profiles.json (agentDir: /home/ubuntu/.clawdbot/agents/main/agent). Configure auth for this agent (clawdbot agents add <id>) or copy auth-profiles.json from the main agentDir.
Logs: clawdbot logs --follow

Hosting on: Private Linux VPS

Using WhatsApp chat instance

And often during messaging I give a task it gets these historical text errors of diff types and stops until I tell it to try again & again.

[Historical context: a different model called tool "gateway" with arguments: {
"raw": "{\n "agents": {\n "defaults": {\n "model": {\n "primary": "google/gemini-3-flash-preview",\n "fallbacks": [\n "google/gemini-3-pro-preview",\n "google/gemini-2.0-flash-exp:free"\n ]\n }\n }\n }\n}",
"action": "config.apply"
}. Do not mimic this format - use proper function calling.]

[Historical context: a different model called tool "exec" with arguments: {
"command": "agent-browser reload && agent-browser snapshot -i --json"
}. Do not mimic this format - use proper function calling.]

[Historical context: a different model called tool "exec" with arguments: {
"command": "agent-browser fill @e2 "APQE%2" && agent-browser click @e3 && agent-browser wait --load networkidle && agent-browser snapshot -i --json"
}. Do not mimic this format - use proper function calling.]

[tawdry hill]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[bright owl]

Found it! This is a known auth issue. Auth is per agent — new agents don't inherit the main agent's API keys.

Quick Fix Options:

Option 1: Copy auth from main agent (fastest)

cp /home/ubuntu/.clawdbot/agents/main/agent/auth-profiles.json /home/ubuntu/.clawdbot/agents/main/agent/

Option 2: Re-run onboarding for that agent

clawdbot agents add anthropic

Option 3: Verify current auth status

clawdbot models status

---

Why this happened:

When you switched to allowlist type, you likely created a new agent instance that doesn't have the Anthropic API key in its auth-profiles.json. Even though your config uses Gemini models, Clawdbot is trying to use Anthropic as a fallback (likely claude-opus-4 or another Anthropic model in your agent defaults).

Pro tip: Check your agent defaults with clawdbot config get agents.defaults.model and make sure fallbacks only include providers you have keys for.

Let me know if that resolves it! 🦐

[bitter spire]

Will option 1 restore my bot back immediately?

@bright owl

@bright owl

[bright owl]

Got the ping! Here's the quick checklist:

1. ✅ Run clawdbot models status to see which providers are configured
2. ✅ Copy the auth-profiles.json if Anthropic is missing
3. ✅ Restart the gateway after fixing: clawdbot gateway restart

If you're still getting historical errors after that, drop the exact error message here and I'll help troubleshoot. The "historical text errors" during messaging usually point to model/fallback config issues.

What's the output when you run clawdbot models status? 🦐

[bitter spire]

Did it not work:

clawdbot config get agents.defaults.model

🦞 Clawdbot 2026.1.24-3 (885167d) — Because Siri wasn't answering at 3AM.

Config path not found: agents.defaults.model

[bright owl]

The config path is wrong. Let me help you find the right one:

1. Check all config first:

clawdbot config get

2. Check auth status (your main issue):

clawdbot models status

3. If auth is missing, add it:

clawdbot agents add anthropic

Or just paste your Anthropic API key when prompted.

---

For your model config, run:

clawdbot config get agents

This will show you the actual path structure. The error you saw means agents.defaults.model isn't the right key path for your config version.

Let me know what clawdbot config get outputs! 🦐

[bitter spire]

Error again:

clawdbot config get
error: missing required argument 'path'

What's wrong? Server has started bug the bot isnt coming right with fboe