Agent shows 'Disconnected'

Last updated Mar 30, 2026

The Disconnected badge appears when the local OpenClaw gateway cannot reach MultiClaw Cloud. In most cases, the gateway has stopped — open Settings > Gateway and click Start gateway to fix it.

Gateway is not running

This is the most common cause. Go to Settings > Gateway and check the gateway status. If it shows as stopped, click Start gateway and wait a few seconds for the agent status to update.

Internet connection is unavailable

The gateway requires internet access to reach MultiClaw Cloud. Verify your machine can load a webpage. If your network is down, the agent will reconnect automatically once connectivity is restored.

MultiClaw Cloud is experiencing an outage

If your gateway is running and you have internet access, check https://status.multiclaw.io for any active incidents. No action is needed on your end — the gateway will reconnect once the service recovers.

Workspace session has expired

Your session can expire after a period of inactivity. Go to Settings > General, scroll to the Account card, and sign in again. The gateway will re-authenticate and the agent should show as connected within a few seconds.

Firewall or proxy blocking the connection

Some corporate firewalls block outbound WebSocket connections. The gateway connects to MultiClaw Cloud over port 443 using the WSS protocol. Ask your IT administrator to allow outbound WSS traffic on port 443 to *.multiclaw.io.

Auth token has expired or been revoked

If signing in again does not help, your local auth token may be corrupted or revoked. Go to Settings > General, scroll to the Account card, sign out completely, then sign back in. This replaces the stored token and typically resolves the issue.

Gateway is running but agent stays disconnected

Transient WebSocket errors can leave the gateway in a stuck state. Go to Settings > Gateway and click Restart gateway. The gateway reconnects with exponential back-off — waiting 30–60 seconds after a brief network interruption often resolves it without a manual restart.

Tip:

If none of the steps above work, check the gateway log at ~/.openclaw/logs/gateway.log for error messages that may point to the cause.