getting no output on responses now | Friends of the Crustacean 🦞🤝 | Page 1

copper chasmBOT Jan 26, 2026, 8:22 PM

#

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

crimson cryptBOT Jan 26, 2026, 8:24 PM

#

The "invalid bearer token" error typically means your Claude OAuth token expired or was invalidated. This commonly happens if you used the same Claude/Codex account in multiple places (Clawdbot + Claude Code CLI can invalidate each other's tokens).

Quick fix:

Generate a fresh setup-token:
```
clawdbot models auth setup-token --provider anthropic
```
Or if you have Claude Code CLI installed elsewhere: run claude setup-token there, then paste it:
```
clawdbot models auth paste-token --provider anthropic
```
Verify:
```
clawdbot models status
```

#

Why this happens:
OAuth tokens can expire or get revoked, especially if you authenticated the same account in multiple clients. The setup-token approach is more stable for subscription accounts.

If you switched to Codex and it's also broken:
The same applies - re-run OAuth for Codex:

clawdbot models auth login --provider openai-codex

Version check:
Before diving deeper, what does clawdbot --version show? Version mismatches can cause weird auth issues too.

Docs: OAuth troubleshooting | Auth setup

ionic plume Jan 26, 2026, 8:25 PM

#

i got this error Error: No Claude Code CLI credentials found after setup-token. Expected auth profile anthropic:claude-cli.

#

@crimson crypt

#

@crimson crypt

crimson cryptBOT Jan 26, 2026, 8:41 PM

#

ionic plume <@1457407575476801641>

Just sharing the thread continuation? The mention @crimson crypt is likely a ping to someone (could be a bot or user).

Do you want me to respond in the thread? If so, I can drop the troubleshooting steps I already prepared.

Or is there something else gala needs help with? 🦐

ionic plume Jan 26, 2026, 8:42 PM

#

yes respond in the thread

crimson cryptBOT Jan 26, 2026, 8:42 PM

#

The "invalid bearer token" error usually means your OAuth token expired or got revoked. This commonly happens if you used the same Claude/Codex account in multiple places (Clawdbot + Claude Code CLI can invalidate each other's tokens).

Quick fix:

Generate a fresh setup-token:
```
clawdbot models auth setup-token --provider anthropic
```
Or if you have Claude Code CLI installed elsewhere: run claude setup-token there, then paste it:
```
clawdbot models auth paste-token --provider anthropic
```
Verify:
```
clawdbot models status
```

#

If you switched to Codex and it's also broken:

clawdbot models auth login --provider openai-codex

Also check:
clawdbot --version — version mismatches can cause weird auth issues too.

Docs: https://docs.clawd.bot/gateway/troubleshooting#oauth-token-refresh-failed-anthropic-claude-subscription | https://docs.clawd.bot/concepts/oauth

crimson cryptBOT Jan 26, 2026, 8:42 PM

#

ionic plume yes respond in the thread

Sent! 🦐

ionic plume Jan 26, 2026, 8:43 PM

#

crimson crypt Sent! 🦐

ot this error Error: No Claude Code CLI credentials found after setup-token. Expected auth profile anthropic:claude-cli.

crimson cryptBOT Jan 26, 2026, 8:44 PM

#

ionic plume ot this error Error: No Claude Code CLI credentials found after setup-token. Exp...

That error means the setup-token was stored, but under a different profile name than what Clawdbot expects. Let's check what profiles you have and fix it:

Check existing auth profiles:

clawdbot models status

Or view the raw profiles:

cat ~/.clawdbot/agents/*/agent/auth-profiles.json 2>/dev/null | jq '.'

Fix options:

If you see an anthropic profile (maybe anthropic:default or similar):
Rename it to match what Clawdbot expects, or update your config to use the existing profile name.

#

Re-run setup-token and specify the profile explicitly:

clawdbot models auth setup-token --provider anthropic --profile anthropic:claude-cli

Or copy the existing profile to the expected location:

# Find the profile file and copy it with the right name

Quick check: What does clawdbot models status show for Anthropic? It should list the available auth profiles.

Docs: Auth profiles

#

The profile is named correctly (anthropic:claude-cli) and the setup-token is stored, but the actual credentials aren't being extracted. This suggests the token might not have been stored properly.

Let's check the raw auth file:

cat ~/.clawdbot/agents/*/agent/auth-profiles.json | jq '.'

Try the paste-token approach instead:

Generate a fresh token: claude setup-token (on any machine with Claude Code)
Then paste it:

clawdbot models auth paste-token --provider anthropic --profile anthropic:claude-cli

Or try re-running setup-token directly:

#

clawdbot models auth setup-token --provider anthropic --profile anthropic:claude-cli

If still failing, check file permissions:

ls -la ~/.clawdbot/agents/*/agent/auth-profiles.json

What do you see when you run those commands? The token might be malformed or there could be a file permission issue.

ionic plume Jan 26, 2026, 9:12 PM

#

crimson crypt ```bash clawdbot models auth setup-token --provider anthropic --profile anthropi...

seems like the token is still static for anthropic

crimson cryptBOT Jan 26, 2026, 9:13 PM

#

ionic plume seems like the token is still static for anthropic

"Static" token likely means the credentials aren't refreshing or the stored token isn't valid for Clawdbot's use.

Nuclear auth reset (start clean):

Wipe existing Anthropic auth:

rm -f ~/.clawdbot/agents/*/agent/auth-profiles.json
rm -f ~/.clawdbot/agents/*/agent/auth.json

Generate fresh setup-token on a machine with Claude Code:
```
claude setup-token
```
Copy the entire token output.
Paste it into Clawdbot:

#

   clawdbot models auth paste-token --provider anthropic

Verify:
```
clawdbot models status
```

Alternative: Use API key instead of OAuth
If you have an Anthropic API key (from console.anthropic.com):

clawdbot models auth api-key --provider anthropic

Also check:

#

clawdbot --version

If you're on an old version, there might be a bug in how setup-tokens are handled. Updating might help:

clawdbot update
clawdbot gateway restart

Which approach do you want to try? 🦐

ionic plume Jan 26, 2026, 9:14 PM

#

crimson crypt "Static" token likely means the credentials aren't refreshing or the stored toke...

getting this back

Screenshot_2026-01-26_at_11.13.52_AM.png

crimson cryptBOT Jan 26, 2026, 9:15 PM

#

ionic plume getting this back

Ah, that's a zsh glob issue! When the wildcard doesn't match any files, zsh throws "no matches found" instead of passing the pattern.

Fix for zsh:

# Option 1: Quote the pattern or use explicit path
rm -f ~/.clawdbot/agents/default/agent/auth-profiles.json
rm -f ~/.clawdbot/agents/default/agent/auth.json

# Option 2: Use nullglob (won't error if no matches)
setopt NULL_GLOB
rm -f ~/.clawdbot/agents/*/agent/auth-profiles.json
rm -f ~/.clawdbot/agents/*/agent/auth.json

Then retry fresh auth:

#

# Generate on machine with Claude Code CLI
claude setup-token

# Paste here
clawdbot models auth paste-token --provider anthropic

# Verify
clawdbot models status

What does ls ~/.clawdbot/agents/ show? That'll confirm the agent directory structure. 🦐

ionic plume Jan 26, 2026, 9:16 PM

#

crimson crypt Ah, that's a **zsh glob issue**! When the wildcard doesn't match any files, zsh ...

i updated clawdbot and got this critical message regarding state integrity

Screenshot_2026-01-26_at_11.16.06_AM.png

crimson cryptBOT Jan 26, 2026, 9:17 PM

#

ionic plume i updated clawdbot and got this critical message regarding state integrity

That's actually good news! 🎉

The "CRITICAL" was just about a missing directory (~/.clawdbot/credentials), and Clawdbot Doctor already fixed it by creating the directory.

Now continue with fresh auth:

# Generate fresh setup-token on a machine with Claude Code CLI
claude setup-token

# Paste it into Clawdbot
clawdbot models auth paste-token --provider anthropic

# Verify
clawdbot models status

#

After this, test a message to see if responses work now. The update likely also fixed any bugs in the auth handling. 🦐

#

I see the issue! You're using a setup-token but it's being stored as a "manual token" (API key format). They look similar but work differently:

API key: sk-ant-api03-... (from console.anthropic.com)
Setup-token: sk-ant-o... (from claude setup-token)

Fix: Use the right auth method for setup-tokens

# Clear the incorrectly stored token
rm -f ~/.clawdbot/agents/main/agent/auth-profiles.json

# Re-add as Claude CLI credentials (not manual token)
clawdbot models auth setup-token --provider anthropic --profile anthropic:claude-cli

# Verify it shows "claude-cli" not "manual token"
clawdbot models status

#

If you don't have Claude Code CLI available, use an API key instead:

# Get an API key from https://console.anthropic.com/
# Then paste it:
clawdbot models auth api-key --provider anthropic

Which auth method do you have access to — Claude Code CLI (claude setup-token) or an Anthropic API key from the console? 🦐

fallen ridge Jan 27, 2026, 3:21 AM

#

@crimson crypt

crimson cryptBOT Jan 27, 2026, 3:22 AM

#

fallen ridge <@1457407575476801641>

Hey disco! 👋 What do you need help with?

If it's related to the OAuth/token issues gala was having, I can share the summary. Or if you have a different issue, just let me know! 🦐

fallen ridge Jan 27, 2026, 3:23 AM

#

crimson crypt Hey disco! 👋 What do you need help with? If it's related to the OAuth/token i...

Providers w/ OAuth/tokens (1): anthropic (1)

anthropic effective=profiles:~/.clawdbot/agents/main/agent/auth-profiles.json | profiles=1 (oauth=0, token=1, api_key=0) | anthropic:default=token

#

at /chat the replies are always U

crimson cryptBOT Jan 27, 2026, 3:24 AM

#

fallen ridge at /chat the replies are always U

"U" as in just the letter U? That's weird — sounds like a truncated response.

A few questions:

What model are you using? (/model in chat or clawdbot models status)
What were you asking about? (What should the full response have been?)
Is it every message or just some?
Does /model status work and show proper auth?

Try a simple test:

Send just "hello" — do you get "U" back or does it hang?
Try /model status — does that reply properly?

This could be:

A streaming truncation issue
Model response getting cut off
Auth issue (model returning empty/error)

#

What's your setup? 🦐

fallen ridge Jan 27, 2026, 3:25 AM

#

crimson crypt "U" as in just the letter U? That's weird — sounds like a truncated response. *...

Current: anthropic/claude-opus-4-5

Switch: /model <provider/model>
Browse: /models (providers) or /models (models)
More: /model status

when I send hello, I get back a U

Current: anthropic/claude-opus-4-5
Default: anthropic/claude-opus-4-5
Agent: main
Auth file: ~/.clawdbot/agents/main/agent/auth-profiles.json

[anthropic] endpoint: default auth: anthropic:default=token:redacted...redacted (next, lastGood) (auth-profiles.json: ~/.clawdbot/agents/main/agent/auth-profiles.json)
• anthropic/claude-opus-4-5 (opus)

fallen ridge Jan 27, 2026, 3:27 AM

#

crimson crypt What's your setup? 🦐

Current: anthropic/claude-opus-4-5

Switch: /model <provider/model>
Browse: /models (providers) or /models (models)
More: /model status

when I send hello, I get back a U

Current: anthropic/claude-opus-4-5
Default: anthropic/claude-opus-4-5
Agent: main
Auth file: ~/.clawdbot/agents/main/agent/auth-profiles.json

[anthropic] endpoint: default auth: anthropic:default=token:redacted...redacted (next, lastGood) (auth-profiles.json: ~/.clawdbot/agents/main/agent/auth-profiles.json)
• anthropic/claude-opus-4-5 (opus)

#

pls ser pls shrimp

fallen ridge Jan 27, 2026, 4:14 AM

#

@krill
HTTP 401: authentication_error: Invalid bearer token
getting this when I message in Telegram.
clawdbot config get channels.telegram.botToken returns the valid token
how can it be?

crimson cryptBOT Jan 27, 2026, 4:18 AM

#

fallen ridge @krill HTTP 401: authentication_error: Invalid bearer token getting this when ...

Based on my research, I believe there's a misunderstanding about where the error is coming from. The "Invalid bearer token" error is NOT from Telegram - it's from your model provider (Anthropic Claude).

Looking at the context:

You mentioned "had things working with claude oauth, but then ran into invalid bearer token problems"
The error format "HTTP 401: authentication_error: Invalid bearer token" matches Anthropic API errors, not Telegram Bot API

The issue: Your Claude OAuth/setup-token has likely expired or become invalid, so when the bot tries to generate a response, the model request fails with a 401.

To fix this:

Check model auth status:
```
clawdbot models status
```
Re-authenticate with Anthropic:

#

   # Option A: Re-run setup-token auth
   clawdbot models auth setup-token --provider anthropic
   
   # Option B: Use API key instead
   clawdbot models auth api-key --provider anthropic

Restart the gateway after re-authenticating:
```
clawdbot gateway restart
```

Why the token shows as valid in config:
clawdbot config get channels.telegram.botToken only shows the Telegram bot token - it has nothing to do with Anthropic auth. The Anthropic token is stored separately in auth profiles.

The Telegram channel is working fine - it's the model's ability to reply that's broken because Claude can't authenticate.

#getting no output on responses now