OpenClaw WebChat Interaction

1. Course Content

Course Overview

OpenClaw WebChat is a browser-based web interaction interface. You do not need to install any client software; simply enter the address in your computer's browser to chat with the robot. This course will provide a detailed introduction to interacting with OpenClaw via WebChat.

Learning Objectives

• Learn to configure WebChat's allowed addresses (Allowed Origins)

• Master the method to access OpenClaw Web UI via browser

• Be able to perform model switching and conversations in the Web interface

• Understand common issues and solutions during WebChat usage

2. Adding Allowed Addresses

• Set the address whitelist for accessing WebChat in the OpenClaw configuration file:

nano $HOME/.openclaw/openclaw.json
# Or use your preferred editor, such as vim, code, etc.

• Find the gateway.controlUi.allowedOrigins configuration item and enter the robot's IP address and port number :18789

• If your robot has multiple IPs, separate them with commas

• The robot's IP can be viewed in several ways, for example by using robot_manage info or by checking the robot's OLED

• Save and exit

  Press Ctrl+O to save, Ctrl+X to exit (nano editor)

• Restart the gateway to apply the configuration

xxxxxxxxxx
openclaw gateway restart

3. Accessing Web UI

• On a computer in the same network segment as the robot, open a browser (regardless of operating system), enter robot IP:18789 in the address bar, and the page will redirect to the gateway dashboard interface

• Enter yahboom in the gateway token field, then click Connect directly

• You will then enter OpenClaw's Web interface, where you can chat with OpenClaw, monitor, and configure parameters

4. Model Switching and Conversation

• In the model option box at the top of the Web interface, you can select a configured model to temporarily switch the current session's model

• After selecting a model, you can chat with OpenClaw in the dialog box

5. Common Conversation Commands

In the WebChat dialog box, besides directly typing text to chat with OpenClaw, you can also use slash commands starting with / to perform various operations. Here are some common conversation commands:

Note: Slash commands must be sent as independent messages (i.e., only the command itself is entered in the dialog box) and cannot be mixed with regular conversation text.

6. Common Errors and Solutions

6.1 Cannot Open the Web Page

Symptoms: After entering the address in the browser, it shows inaccessible or connection timeout.

Possible causes and solutions:

• Robot gateway not running — Make sure OpenClaw Gateway is started; run openclaw gateway status to check the status

• Network unreachable — Confirm that the computer and the robot are on the same LAN; use ping robot IP to test connectivity

• Port not open — Confirm that the access address and port number are correct (should be robot IP:18789)

• Firewall blocked — Check whether the robot's firewall allows port 18789

6.2 Token Verification Failed

Symptoms: After entering the token, it reports authentication failure and cannot connect.

Possible causes and solutions:

• Incorrect token entered — Make sure to enter yahboom in the token field (note case sensitivity)

• Token configuration modified — Check whether the value of the gateway.controlUi.authToken item in openclaw.json matches what you entered

6.3 No Response or Model Loading Failed

Symptoms: You successfully enter the Web interface, but OpenClaw does not reply after you send a message.

Possible causes and solutions:

• Model not configured correctly — Run openclaw models list and openclaw models status in the terminal to check whether the model is configured and available

• API-KEY not set or expired — Refer to the API-KEY configuration chapter to reconfigure

• Model switching exception — Try re-selecting the model using the /model command in the dialog box

• Gateway connection lost — Restart the gateway: openclaw gateway restart

6.4 Allowed Addresses Configuration Not Taking Effect

Symptoms: Still cannot access even after filling in allowedOrigins.

Possible causes and solutions:

• Gateway not restarted — After modifying the configuration file, you must run openclaw gateway restart for changes to take effect

• IP address filled in incorrectly — Use ip a or ifconfig to confirm the robot's actual IP address

• Configuration item in the wrong location — Confirm that allowedOrigins is under the gateway.controlUi node, not elsewhere