Bot disconnected | Friends of the Crustacean 🦞🤝 | Page 1

blazing elkBOT Jan 28, 2026, 1:39 PM

#

Hey! 👋 🦐 The 1006 error means the WebSocket connection closed abnormally (no close frame was received). This can happen for a few reasons:

Common causes:

Network instability – Check your server's connection stability
Rate limiting – Too many events/actions in a short window
Outdated gateway – Make sure you're running the latest Clawdbot version
Resource issues – Low memory/CPU on the host
Gateway负载 – Discord sometimes has transient issues

Quick troubleshooting:

moltbot --version –确认版本
Check logs around the disconnection time: clawdbot logs or clawdbot gateway logs
Verify network connectivity from the host
If running on a VPS, check if it's being rate-limited

Relevant docs:

Troubleshooting: https://docs.moltbot.ai/gateway/troubleshooting

#

FAQ: https://docs.moltbot.ai/start/faq

Got a version number I can check? That usually narrows it down fast! 🦐

#

Ah, that's the issue! 🎯

The moltbot command is an npx shim and its cache is corrupted. This is a known npx quirk – the package.json is missing from the cached installation.

Quick fix:

# Clear npx cache
npm cache clean --force

# Or if using pnpm
pnpm store prune

# Then try
moltbot --version

However, for a more stable setup, I'd recommend installing Clawdbot properly instead of relying on npx:

#

npm install -g clawdbot

Since you're seeing version 1.7.1-dev.0 for clawdbot, you're actually running Clawdbot, not the old moltbot package. The moltbot npx wrapper is just broken.

For the 1006 disconnects: Once the moltbot command issue is fixed, run:

clawdbot logs

And check what the actual error is before the disconnect. The 1006 is just "connection died" – the logs will tell us why. Common culprits:

Invalid token (check ~/.clawdbot/config.json5)
Gateway intents misconfigured
Network blips

#

Try the cache clean first and let me know if --version works after that! 🦐

#

Great, that's fixed! 🎉 Clawdbot 1.6.1 is showing properly now.

Now let's tackle that 1006 disconnect. Run:

clawdbot logs

Or for more detail:

clawdbot gateway logs

Look for any error messages right before the disconnect timestamp. The 1006 just means "connection died unexpectedly" – the logs will tell us the real reason (token issue, rate limit, network, etc.).

Also check:

#

clawdbot gateway status

What do the logs show? 🦐

#

The gateway isn't running at all – that's why you're getting 1006! 😅

Start it up:

clawdbot gateway start

Or if that doesn't work:

clawdbot start

The gateway status shows Status: not_running and Gateway: disconnected – the bot is trying to connect but there's nothing to connect to.

Once started, run clawdbot logs to see the connection in action. If it starts fine, the issue was just that the gateway wasn't running. If it crashes, the logs will tell us why! 🦐

obsidian cedar Jan 28, 2026, 3:00 PM

#

@blazing elk when o use codex my clawdbot works fine when i use antigravity in the antigravity app it works but when i use antigravity on clawdbot it doesnt work why?

blazing elkBOT Jan 28, 2026, 3:02 PM

#

obsidian cedar <@1457407575476801641> when o use codex my clawdbot works fine when i use antigr...

Hey! 👋 🦐

This is usually a model configuration issue. Antigravity (Claude Code's mode) requires specific model access that's not configured in Clawdbot by default.

Check your config:

clawdbot config get
# or
cat ~/.clawdbot/config.json5

Look for the model setting. Antigravity likely needs a different model endpoint or key.

Also check:

Do you have a separate API key for Antigravity/Claude Code?
Is the model name different from what Codex uses?

#

For model-specific help: Head to #models (channel: 1456704705219661980) – they have hands-on experience with different model configs and can help you get Antigravity working! 📊

https://docs.moltbot.ai/concepts/models

Let me know what your current model config looks like and I can help troubleshoot further! 🦐

fringe flare Jan 28, 2026, 3:06 PM

#

How do I find the chrome relay extension

blazing elkBOT Jan 28, 2026, 3:06 PM

#

fringe flare How do I find the chrome relay extension

Hey! 🦐 The Chrome Relay extension is available in the Chrome Web Store:

🔗 https://chrome.google.com/webstore/detail/clawdbot-browser-relay/

To install:

Click the link above
Hit "Add to Chrome"
Once installed, you'll see a clawdbot icon in your Chrome toolbar

When using browser features in Clawdbot:

Click the extension icon on the tab you want to control
It should show "Clawdbot Browser Relay: ON"

https://docs.moltbot.ai/clients/browser

Let me know if you need help with the actual browser control setup! 🦐

#

That's normal! 😄 The extension icon is just a launcher. Here's how it actually works:

To attach a tab to Clawdbot's browser relay:

Navigate to the website you want Clawdbot to control
Click the Clawdbot extension icon (🦞 or clawdbot icon) in your Chrome toolbar
The badge should change to show "ON" or "Attached"

What it looks like when attached:

Badge shows: "Clawdbot: ON" or similar
The extension is now listening for Clawdbot commands

Then in Clawdbot, you can use:

# List attached tabs
clawdbot browser status

#

Let me help you troubleshoot! A few things to check:

1. Pin the extension first:

Click the puzzle piece icon 🧩 in your Chrome toolbar
Find "Clawdbot Browser Relay"
Click the pin icon 📌 next to it

2. Check if it's actually installed:

Go to chrome://extensions/ in your address bar
Look for "Clawdbot Browser Relay"
Make sure the toggle is ON (enabled)

3. Try these steps:

Refresh the page after clicking the extension
Try a different website (like google.com)
Make sure Chrome is fully updated

#

4. If still nothing:

Disable and re-enable the extension
Remove and reinstall from the Chrome Web Store

https://docs.moltbot.ai/clients/browser

Let me know what you see in chrome://extensions/ or if the pin icon helps! 🦐

fringe flare Jan 28, 2026, 7:47 PM

#

How do I fix this

#

#

?

blazing elkBOT Jan 28, 2026, 7:51 PM

#

fringe flare How do I fix this

That looks like the gateway crashed or stopped running again. Let's check and restart it:

1. Check gateway status:

clawdbot gateway status

2. If not running, start it:

clawdbot gateway start

3. Check the logs to see why it crashed:

clawdbot logs

fringe flare Jan 28, 2026, 7:53 PM

#

Got this message

#

Ran logs and got this

blazing elkBOT Jan 28, 2026, 7:54 PM

#

fringe flare

Gateway is not running – that's why you're getting the "not connected" message! 🦐

Just start it:

clawdbot gateway start

Then check status again:

clawdbot gateway status

It should show Status: running and Gateway: connected once it's up.

If it fails to start or crashes immediately:

#

The logs will tell us what happened. Common causes:

Token expired or was revoked
Rate limiting
Resource issues on your host
Network instability

Run those commands and paste the output here! 🦐

#

clawdbot logs

That'll show us what went wrong (token issue, config problem, etc.).

Try starting it first and let me know what happens! 🚀

fringe flare Jan 28, 2026, 7:57 PM

#

#

This is what I got

blazing elkBOT Jan 28, 2026, 8:03 PM

#

fringe flare Ran logs and got this

Ah, the gateway started but immediately disconnected with 1006. The logs say "no reason provided" but there are a few common causes:

Most likely: Token issue

Check your bot token in the config
The token might be invalid, expired, or revoked

Check your config:

clawdbot config get | grep -i token
# Or check the config file directly
cat ~/.clawdbot/config.json5

Quick things to verify:

Is the bot still in your Discord server?
Did you regenerate the token recently?
Are all required Gateway Intents enabled in the Discord Developer Portal?

blazing elkBOT Jan 28, 2026, 8:04 PM

#

fringe flare This is what I got

I don't see an image attached to your last message! Could you re-upload or describe what you're seeing? 🦐

#

To check intents:

Go to https://discord.com/developers/applications
Select your bot
Click "Bot" in the left sidebar
Scroll down to "Privileged Gateway Intents"
Make sure necessary intents are enabled (Message Content, Server Members, etc.)

If the token is wrong, you'll need to update it in your config:

clawdbot config patch '{"token": "your-new-token-here"}'

What does your token config look like? 🦐

fringe flare Jan 28, 2026, 8:05 PM

#

This is on my Mac mini it was working and then randomly stopped

blazing elkBOT Jan 28, 2026, 8:07 PM

#

fringe flare This is on my Mac mini it was working and then randomly stopped

Since it was working and just stopped randomly, a few things could have changed:

Quick checks:

Is the bot still in your server?
- Check if the bot user is still in your Discord server
- If it was kicked or banned, that would cause immediate 1006 disconnects
Check Discord developer portal:
- Go to https://discord.com/developers/applications
- Verify the bot is still listed
- Check if the token changed or was reset
Run this to see your full config (without exposing full token):
```
clawdbot config get
```

#

Check for system changes:
- Did you restart your Mac mini?
- Update macOS or Chrome?
- Change network/VPN?

Also try:

clawdbot gateway restart

And check logs again:

clawdbot logs

Let me know what clawdbot config get shows (you can mask the token if you want) and if the bot is still in your server! 🦐

fringe flare Jan 28, 2026, 8:07 PM

#

That’s what is says about my config

#

Also I didn’t setup on discord

blazing elkBOT Jan 28, 2026, 8:09 PM

#

fringe flare That’s what is says about my config

The config looks correct! Token is masked, settings look fine. Since it was working and randomly stopped, the issue is likely one of these:

Most likely:

Bot got kicked from the server
- Check if the bot is still in your Discord server
- If not, re-invite it with the correct OAuth2 URL
Token was revoked
- Go to https://discord.com/developers/applications
- Check if the bot still exists
- If not, create a new bot and get a fresh token
OAuth2 permissions changed
- If you use OAuth2 invite, new permissions might be required

Quick check:

#

# Check if bot is in server (if you have other sessions connected)
clawdbot gateway status

# Or try to re-invite the bot from Discord Developer Portal

To re-invite:

Go to Discord Developer Portal
Select your app
Click "OAuth2" → "URL Generator"
Generate invite URL with proper scopes (bot + applications.commands)
Re-invite to your server

Is the bot still showing up in your server members list? 🦐

fringe flare Jan 28, 2026, 8:10 PM

#

But I didn’t setup on discord I did this through the terminal

blazing elkBOT Jan 28, 2026, 8:10 PM

#

fringe flare But I didn’t setup on discord I did this through the terminal

Ah, that's important context! 🦐

How did you initially set it up? Was it through:

clawdbot login discord ?
The OAuth URL flow in terminal?
Or did you paste a token directly?

Try restarting fresh:

# Stop everything
clawdbot gateway stop

# Clear any stuck state
clawdbot gateway restart

# Check status

#

clawdbot gateway status

# If still failing, check detailed logs
clawdbot logs --tail 50

Also check if there's a Discord session issue:

clawdbot sessions list

The fact it worked then randomly stopped suggests:

Network blip on your Mac mini
Discord server had an issue
Or the auth session expired

#

What setup command did you run originally? That'll help me guide you better! 🦐

fringe flare Jan 28, 2026, 8:12 PM

#

I just ran it to my terminal from the clawdbot website… and it says launch agent not loaded config issue

blazing elkBOT Jan 28, 2026, 8:12 PM

#

fringe flare I just ran it to my terminal from the clawdbot website… and it says launch agent...

Found it! 🎯 "Launch agent not loaded" means the macOS service itself has a config problem.

Check the launch agent status:

# List launch agents
launchctl list | grep -i clawdbot

# Or check if the plist exists
ls ~/Library/LaunchAgents/

Try reloading the launch agent:

# Unload first
launchctl unload ~/Library/LaunchAgents/ai.clawdbot.gateway.plist 2>/dev/null

#

# Then reload
launchctl load ~/Library/LaunchAgents/ai.clawdbot.gateway.plist

Or just bypass the launch agent entirely for testing:

# Run gateway directly (not as a service)
clawdbot gateway run

This will start it in foreground and show you the actual error instead of the launch agent issue.

If the plist is missing/corrupted, reinstall:

clawdbot gateway install

#

Try clawdbot gateway run first – that'll tell us what the actual error is behind the scenes! 🦐

fringe flare Jan 28, 2026, 8:14 PM

#

Service: LaunchAgent (not loaded)
File logs: /tmp/clawdbot/clawdbot-2026-01-28.log
Command: /opt/homebrew/bin/node /opt/homebrew/lib/node_modules/clawdbot/dist/entry.js gateway --port 18789
Service file: ~/Library/LaunchAgents/com.clawdbot.gateway.plist
Service env: CLAWDBOT_GATEWAY_PORT=18789

Config (cli): ~/.clawdbot/clawdbot.json (invalid)
Config issue: agents.defaults.memorySearch.experimental.sessionMemory: Invalid input: expected boolean, received object
Config (service): ~/.clawdbot/clawdbot.json (invalid)
Service config issue: agents.defaults.memorySearch.experimental.sessionMemory: Invalid input: expected boolean, received object

#

\

#

Config invalid
File: ~/.clawdbot/clawdbot.json
Problem:

agents.defaults.memorySearch.experimental.sessionMemory: Invalid input: expected boolean, received object

blazing elkBOT Jan 28, 2026, 8:18 PM

#

fringe flare Config invalid File: ~/.clawdbot/clawdbot.json Problem: - agents.defaults.memo...

Found the root cause! 🎯 Your config has an invalid structure for sessionMemory.

Fix it by editing your config:

clawdbot config edit

Look for this section and fix it:

{
  agents: {
    defaults: {
      memorySearch: {
        experimental: {
          // WRONG: sessionMemory is an object

#

          // sessionMemory: { something: true }
          
          // RIGHT: sessionMemory should be a boolean
          sessionMemory: true
        }
      }
    }
  }
}

Or patch it directly:

clawdbot config patch '{"agents":{"defaults":{"memorySearch":{"experimental":{"sessionMemory":true}}}}}'

#

Then restart the gateway:

clawdbot gateway restart

The error says sessionMemory expected a boolean (true/false) but got an object (curly braces {}). Just delete the object and set it to true or false!

Let me know once you've patched it! 🦐

fringe flare Jan 28, 2026, 8:19 PM

#

dbot config patch '{"agents":{"defaults":{"memorySearch":{"experimental":{"sessionMemory":true}}}}}'
Invalid config at /Users/oscarclark/.clawdbot/clawdbot.json:\n- agents.defaults.memorySearch.experimental.sessionMemory: Invalid input: expected boolean, received object
error: too many arguments for 'config'. Expected 0 arguments but got 2.

blazing elkBOT Jan 28, 2026, 8:20 PM

#

fringe flare dbot config patch '{"agents":{"defaults":{"memorySearch":{"experimental":{"sessi...

You need to use clawdbot at the start! Try:

clawdbot config patch '{"agents":{"defaults":{"memorySearch":{"experimental":{"sessionMemory":true}}}}}'

Make sure you include the full clawdbot command, not just dbot! 🦐

#Bot disconnected