anthropic token expired

[tawny shuttle]

how do I refresh it?

[naive trellis]

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

[modern geyser]

To refresh an Anthropic API key:

1. Go to console.anthropic.com
2. Sign in to your account
3. Navigate to Settings → API Keys (or Credits & Billing)
4. Create a new API key or check if your credits need replenishing
5. Update your Clawdbot config with the new key:

   clawdbot configure anthropic
   

   or manually edit ~/.clawdbot/clawdbot.json:

   {
     "anthropic": {
       "apiKey": "sk-ant-new-key-here"
     }
   

   }

If you're seeing "token expired" errors, it's usually:

• The API key was revoked/rotated
• Credits ran out
• Account needs verification

Check your Console first to see the actual status of your account/key. 🦐

[tawny shuttle]

not the api but the token

[modern geyser]

Ah, you're talking about the Claude Code CLI token (for claude command-line tool), not the API key.

To refresh that token:

1. Run: claude auth refresh
2. Or log out and back in: claude auth logout → claude auth login

If that doesn't work, check your Claude Code settings at claude.com/settings for active sessions/tokens.

I don't have the full Claude CLI auth docs memorized — if those commands don't work, let me know and I can look up the current auth flow! 🦐

[tawny shuttle]

I am in claude code now and refresh my auth. how do I tie that back in with Clawdbot

[modern geyser]

Clawdbot and Claude Code CLI are separate — the auth you refreshed in Claude Code CLI doesn't automatically carry over to Clawdbot.

Two possibilities:

1. If you're using Anthropic API in Clawdbot (standard setup):

   • Clawdbot uses its own API key
   • Run: clawdbot configure anthropic to update it
   • Or check ~/.clawdbot/clawdbot.json has the correct apiKey

2. If you're using Claude Code CLI as a tool in Clawdbot:

   • Let me check your config — do you have Claude Code integrated as an agent/tool?
   • If so, the CLI auth should work, but you may need to restart Clawdbot to pick up the new token

Which setup are you running? I can check your config to see how Clawdbot is connecting to Anthropic. 🦐

[tawny shuttle]

Agent failed before reply: OAuth token refresh failed for anthropic: Failed to refresh OAuth token for anthropic. Please try again or re-authenticate.. Check gateway logs for details.

[modern geyser]

Clawdbot's OAuth token refresh failed. You have two options:

Option 1: Re-authenticate with Clawdbot

clawdbot configure

Then go through the Anthropic OAuth flow again.

Option 2: Switch to API Key (simpler, more reliable)

clawdbot configure anthropic

Paste in your Anthropic API key instead of using OAuth. This avoids token refresh issues entirely.

The API key approach is generally more stable for server deployments. Just get a new key from console.anthropic.com and paste it in. 🦐

[tawny shuttle]

it says the cladue code cli the token has expired. but I am in claude code and not sure how refresh the token in clawdbot

[modern geyser]

The token that expired is Clawdbot's Anthropic OAuth token, not your Claude Code CLI.

To fix it in Clawdbot:

clawdbot configure

Then re-authenticate with Anthropic when prompted.

Your Claude Code CLI token is separate — it has nothing to do with Clawdbot. Clawdbot has its own OAuth connection that needs its own fresh token. 🦐

[tawny shuttle]

"auth": {
"profiles": {
"anthropic:claude-cli": {
"provider": "anthropic",
"mode": "oauth"
}
}
},

[modern geyser]

That's an OAuth profile for anthropic:claude-cli. To refresh it:

clawdbot configure anthropic:claude-cli

This will trigger a fresh OAuth flow and update the token.

If that doesn't work, you can:

1. Edit ~/.clawdbot/clawdbot.json and remove the auth.profiles.anthropic:claude-cli section
2. Run clawdbot configure to re-authenticate from scratch

Or just switch to API key mode with clawdbot configure anthropic — OAuth tokens expire and require periodic re-auth, while API keys don't. 🦐

[tawny shuttle]

just tried and still no luck

[modern geyser]

Frustrating! Let's try a different approach:

Step 1: Remove the OAuth profile from config
Edit ~/.clawdbot/clawdbot.json and delete the entire auth.profiles.anthropic:claude-cli section.

Step 2: Check your gateway logs for the real error

clawdbot gateway logs --tail=50

Look for the actual Anthropic error — it might reveal why refresh keeps failing.

Step 3: Switch to API key (most reliable)

clawdbot configure anthropic

Paste your API key instead of OAuth. This avoids the token expiry headache entirely.

OAuth tokens for Anthropic can be finicky in server environments. An API key is much more stable for Clawdbot. 🦐

[shell glade]

use setup-token