#Clawdbot UI

1 messages · Page 1 of 1 (latest)

unique ravine
#

Hello, I just installed Clawdbot on windows, onboarded (linked telegram) and started gateway. When clawdbot control pops up nothing is populating. Help?

fading quailBOT
#

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

unique ravine
#

Shouldn't a message populate that says "Wake up, my friend!" and go on from there?

grand phoenixBOT
# unique ravine Hello, I just installed Clawdbot on windows, onboarded (linked telegram) and sta...

Based on the docs, here are the most common causes and fixes for the Control UI not populating on Windows:

Quick Checks

1. Gateway Running?
Open a terminal and run:

moltbot gateway status

The gateway must be running before the Control UI will work.

2. Open the Right URL
Use http://127.0.0.1:18789/ (not a LAN IP). Accessing over plain HTTP from a LAN IP blocks WebCrypto and device identity.

3. Check Logs

# 
moltbot logs --follow

Look for errors about connection, auth, or the WebSocket.

Common Fixes

If the gateway isn't running:

moltbot gateway

If you're using a LAN IP or Tailscale IP:

If the page loads but nothing populates:

#
  • Check browser console (F12) for errors
  • Ensure no ad blocker or extension is interfering
  • Try a different browser (Chrome/Edge)

Service running but nothing on the port:

moltbot doctor
schtasks /Query /TN "Moltbot Gateway" /V /FO LIST

Windows-specific:
Make sure Windows Defender or other security software isn't blocking the connection.

Can you run moltbot gateway status and share the output? That'll show if the gateway is actually running and what port it's bound to. 🦐

unique ravine
#

PS C:\Users\jacob> clawdbot gateway status

🦞 Clawdbot 2026.1.24-3 (885167d) — Your AI assistant, now without the $3,499 headset.

│
◇
Service: Scheduled Task (registered)
File logs: \tmp\clawdbot\clawdbot-2026-01-29.log
Command: C:Program Filesnodejsnode.exe C:UsersjacobAppDataRoamingnpmnode_modulesclawdbotdistentry.js gateway --port 18789
Service env: CLAWDBOT_GATEWAY_PORT=18789

Config (cli): C:\Users\jacob.clawdbot\clawdbot.json
Config (service): C:\Users\jacob.clawdbot\clawdbot.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: running (last run time 1/29/2026 2:47:06 PM)
RPC probe: ok

Listening: 127.0.0.1:18789
Troubles: run clawdbot status
Troubleshooting: https://docs.clawd.bot/troubleshooting

grand phoenixBOT
# unique ravine PS C:\Users\jacob> clawdbot gateway status 🦞 Clawdbot 2026.1.24-3 (885167d) — ...

The gateway is running correctly! The issue is on the browser side. Here's how to fix it:

Quick Fixes

1. Open directly in browser
Go to: http://127.0.0.1:18789/ (exactly this, not localhost, not with a trailing slash)

2. Try a different browser
If you're using Firefox, try Chrome or Edge. Firefox sometimes has stricter WebSocket handling.

3. Check browser console
Press F12 → Console tab → look for red errors (WebSocket connection failures, CORS issues)

4. Clear browser data
Clear cookies/site data for 127.0.0.1

5. Disable extensions

#

Ad blockers or privacy extensions can interfere with WebSocket connections

If still not working

Check if something's actually listening:

netstat -an | findstr 18789

You should see TCP 127.0.0.1:18789 0.0.0.0:0 LISTENING

Check the gateway logs:

clawdbot logs --follow

Then refresh the browser page — you should see activity in the logs.

#

Let me know what you see in the browser console (F12) or if the netstat command shows the port listening. 🦐

unique ravine