Blank message on clawdbot UI | Friends of the Crustacean 🦞🤝 | Page 1

silent hull Jan 27, 2026, 7:18 AM

#

I've connected to Minimax 2.1 model, but I'm not sure why it doesn't reply anything

#

@flint phoenix please help

flint phoenixBOT Jan 27, 2026, 7:20 AM

#

Hey! 🦐 Let me help you troubleshoot the Minimax 2.1 no-reply issue.

First, let's check a few things:

Run clawdbot --version — version mismatches cause weird issues
Check the logs for errors:
```
clawdbot logs --follow
```
Then send a test message and look for errors like:
- Unknown model: minimax/MiniMax-M2.1
- Authentication errors
- Provider connection failures
Verify auth is set up correctly:

#

   clawdbot models status

Common MiniMax issues:

Some MiniMax plans need special handling — check the GitHub issue tracker for recent fixes
The /model command may not always take effect immediately (known bug #646)
Try restarting the gateway: clawdbot gateway restart

If it still doesn't work:

Try a different model temporarily to isolate the issue
Check if your MiniMax quota/rate limits are hit

Could you run those commands and share the outputs (redact any secrets)? That'll help pinpoint the exact issue! 🦐

flint phoenixBOT Jan 27, 2026, 7:21 AM

#

silent hull I've connected to Minimax 2.1 model, but I'm not sure why it doesn't reply anyth...

I sent a detailed troubleshooting response in the Discord thread. The key points I covered:

Version check first (clawdbot --version) — critical for diagnosing issues
Log investigation — to find the actual error
Model status check — to verify auth is working
Common MiniMax issues — including the known /model command bug (#646) and plan-specific quirks
Gateway restart — sometimes fixes transient issues

The user should run those diagnostic commands and share the outputs so we can pinpoint whether it's an auth problem, quota issue, or something else. 🦐

silent hull Jan 27, 2026, 7:29 AM

#

HTTP 401 authentication_error: login fail: Please carry the API secret key in the 'Authorization' field of the request
header (request_id: 05c7990fbbc5acbf3a114bbec5b3470f)
gateway connected | idle
agent main | session main | minimax/MiniMax-M2.1 | tokens 0/200k (0%)

#

@flint phoenix

silent hull Jan 27, 2026, 7:52 AM

#

now my chat is disconnect, the error is disconnected (1008): unauthorized: gateway token mismatch (open a tokenized dashboard URL or paste token in Control UI settings)

#

@flint phoenix

flint phoenixBOT Jan 27, 2026, 7:53 AM

#

Hey! 👋 Got your tag! 🦐

Have you had a chance to run those diagnostic commands? I'm looking for:

clawdbot --version
clawdbot logs --follow (while sending a test message)
clawdbot models status

Any of those outputs will help me figure out why Minimax isn't replying! Let me know what you find. 🦐

flint phoenixBOT Jan 27, 2026, 7:54 AM

#

silent hull <@1457407575476801641>

Tagged you back! 🦐 Now waiting on the diagnostic outputs (version, logs, models status) to see what's actually happening with Minimax.

silent hull Jan 27, 2026, 8:00 AM

#

clawdbot --version : 2026.1.24-3 and the picture is the output when I entered clawdbot logs --follow. the clawdbot models status:
🦞 Clawdbot 2026.1.24-3 (885167d) — If something's on fire, I can't extinguish it—but I can write a beautiful postmortem.

Config : C:\Users\14185.clawdbot\clawdbot.json
Agent dir : C:\Users\14185.clawdbot\agents\main\agent
Default : minimax/MiniMax-M2.1
Fallbacks (0) : -
Image model : -
Image fallbacks (0): -
Aliases (1) : Minimax -> minimax/MiniMax-M2.1
Configured models (2): google-antigravity/claude-opus-4-5-thinking, minimax/MiniMax-M2.1

Auth overview
Auth store : C:\Users\14185.clawdbot\agents\main\agent\auth-profiles.json
Shell env : off
Providers w/ OAuth/tokens (1): google-antigravity (1)

google-antigravity effective=profiles:C:\Users\14185.clawdbot\agents\main\agent\auth-profiles.json | profiles=1 (oauth=1, token=0, api_key=0) | google-antigravity:y7m91104@gmail.com=OAuth (y7m91104@gmail.com)
minimax effective=profiles:C:\Users\14185.clawdbot\agents\main\agent\auth-profiles.json | profiles=1 (oauth=0, token=0, api_key=1) | minimax:default=sk-cp-Tu...PP129FVc

OAuth/token status

google-antigravity usage: gemini-3-pro-high 100% left ⏱6d 23h · gemini-2.5-flash 100% left ⏱4h 59m
- google-antigravity:y7m91104@gmail.com (y7m91104@gmail.com) expiring expires in 45m

#

@flint phoenix

flint phoenixBOT Jan 27, 2026, 8:01 AM

#

Thanks for the diagnostics! 🦐 I can see:

Good news:

Version is current (2026.1.24-3) ✅
Minimax API key is configured ✅
Model is set as default ✅

I need to see the actual logs when you send a message — the image shows the log file exists but not what happens when you try to chat.

Try this:

In one terminal run: clawdbot logs --follow
In Discord, send a test message to Clawdbot
Copy what appears in the logs

Also, try adding a fallback model in your config — this will help us see if minimax is failing silently:

#

{
  "models": {
    "fallbacks": ["google-antigravity/claude-opus-4-5-thinking"]
  }
}

Then run clawdbot gateway restart and try again.

If the fallback model replies but minimax doesn't, we know minimax is failing (could be quota, API key issue, or provider problem).

Let me know what the logs show! 🦐

flint phoenixBOT Jan 27, 2026, 8:02 AM

#

silent hull clawdbot --version : 2026.1.24-3 and the picture is the output when I en...

Asked for the actual log output when sending a message and suggested adding fallbacks to isolate whether Minimax is silently failing. This will help us see if it's an API key issue, quota problem, or provider failure. 🦐

silent hull Jan 27, 2026, 8:03 AM

#

I can't send message to clawdbot either on discord or telegram because I haven't pair yet, now I'm just trying to figure out why is my clawd bot UI disconnected: disconnected (1008): unauthorized: gateway token mismatch (open a tokenized dashboard URL or paste token in Control UI settings) @flint phoenix

flint phoenixBOT Jan 27, 2026, 8:03 AM

#

silent hull I can't send message to clawdbot either on discord or telegram because I haven'...

Ah! That's the real issue then! 🎯 You can't test the model until you get the UI connected. The "gateway token mismatch" is blocking everything.

To fix the UI connection:

Open the dashboard — run this in terminal:
```
clawdbot dashboard
```
This should open a browser with a fresh tokenized URL.
If that doesn't work, get a new token:
```
clawdbot gateway token
```
Then paste it in your Control UI settings.
On Windows specifically, make sure the Gateway service is actually running:

#

   clawdbot gateway status

Once you're connected to the UI, you can:

Complete the WhatsApp pairing (scan the QR)
Test the Minimax model properly

Quick fix path:

clawdbot dashboard

Copy the URL it opens, paste it in browser, and you should be connected! 🦐

Let me know if that gets the UI connected!

silent hull Jan 27, 2026, 8:05 AM

#

I got connected now, and it still reply with the blank message, now how do I pair with my telegram? @flint phoenix

flint phoenixBOT Jan 27, 2026, 8:06 AM

#

Great! 🎉 Now for Telegram pairing:

Option 1: Through the Dashboard (easiest)

In your Clawdbot dashboard, look for Channels or Settings
Find Telegram section
Enter your bot token (see Option 2 if you don't have one)
Save and restart the gateway

Option 2: Get a Telegram Bot Token

Open Telegram, message @BotFather: /newbot
Follow the prompts to name your bot
Copy the HTTP API token it gives you
Paste that token in the Clawdbot dashboard or config

To allow access (DMs):
In your config, add your user ID:

#

{
  "channels": {
    "telegram": {
      "token": "YOUR_BOT_TOKEN",
      "allowFrom": ["YOUR_TELEGRAM_USER_ID"]
    }
  }
}

To find your Telegram user ID:

DM @userinfobot or @getidsbot on Telegram
Or check the logs after messaging your bot

Once configured, restart the gateway and your bot will respond to DMs! 🦐

#

Do you already have a bot token, or need help creating one? 🦐

flint phoenixBOT Jan 27, 2026, 8:06 AM

#

silent hull I got connected now, and it still reply with the blank message, now how do I pai...

Gave them the Telegram setup steps — either through the dashboard or creating a new bot via BotFather. Once connected, they can properly test the Minimax model! 🦐

silent hull Jan 27, 2026, 8:15 AM

#

This is the channels from dashboard, where do I put my user id and how do I know my token of telegram?

#

@flint phoenix

flint phoenixBOT Jan 27, 2026, 8:16 AM

#

Perfect, I can see the channel settings! Here's what to do:

1. Get your Telegram User ID:

Open Telegram and message @userinfobot
It will reply with your user ID (a number like 123456789)
Copy that number

2. Get/Create your Bot Token:

Message @BotFather on Telegram
Send /newbot
Give your bot a name (e.g., "My Assistant")
Give it a username ending in "bot" (e.g., "myassistant_bot")
BotFather will reply with a long token — copy that!

3. Add them to Clawdbot:
In the dashboard's Channel settings, add:

Token: YOUR_BOT_TOKEN (from BotFather)

#

Allow from: YOUR_USER_ID (from userinfobot, as a number)

Save the settings, then run:

clawdbot gateway restart

Quick test: Message your bot on Telegram with /start — it should reply! 🦐

Let me know if you hit any issues! 🦐

flint phoenixBOT Jan 27, 2026, 8:16 AM

#

silent hull This is the channels from dashboard, where do I put my user id and how do I know...

Gave them the full walkthrough — message @userinfobot for their ID and @BotFather to create/get the bot token. Once both are added to the dashboard and the gateway restarts, Telegram should work! 🦐

silent hull Jan 27, 2026, 8:24 AM

#

I've done everything you told me to do, but when I text/start to my bot it says: HTTP 401: authentication_error: login fail: Please carry the API secret key in the 'Authorization' field of the request header (request_id: 05c7a82fe8b62f95e94f79b029e966ea). And the dashboard channel says Unsupported schema node. Use Raw mode.

#

@flint phoenix

flint phoenixBOT Jan 27, 2026, 8:26 AM

#

silent hull I've done everything you told me to do, but when I text/start to my bot it says:...

I see the issue! The Telegram config key is botToken, not token. Also, the dashboard shows "Unsupported schema node" — you need to edit the config file directly.

Here's the fix:

Open your config file:
- On Windows: C:\Users\14185\.clawdbot\clawdbot.json
- Edit it with any text editor (Notepad, VS Code, etc.)
Make sure it looks like this:

{
  "channels": {
    "telegram": {
      "enabled": true,
      "botToken": "YOUR_BOT_TOKEN_HERE",
      "dmPolicy": "pairing",

#

      "allowFrom": ["YOUR_USER_ID"]
    }
  }
}

Important: The key is botToken (not token) and make sure there are no spaces in the token format like 123:ABC....

Save the file and restart:

clawdbot gateway restart

Test: Message your bot with /start on Telegram

Common token mistakes:

#

Don't add extra spaces around the :
Format should be exactly 123456:ABC-123... (number colon hash string)
Make sure you copied the full token from BotFather

Try editing the config file directly and let me know what happens! 🦐

silent hull Jan 27, 2026, 8:33 AM

#

No, the botToken is the exact as the botfather provided, and the error still exist when I text /start, the error is HTTP 401: authentication_error: login fail: Please carry the API secret key in the 'Authorization' field of the request header (request_id: 05c7a82fe8b62f95e94f79b029e966ea)

#Blank message on clawdbot UI