Welcome to MicroROS V2 Robot Car repository
1. Openclaw Webchat Interaction
OpenClaw WebChat Interaction
OpenClaw WebChat Interaction1. Course ContentCourse OverviewLearning Objectives2. Add Allowed Addresses3. Enter the Web UI4. Model Switching and Conversation5. Common Session Commands6. Common Errors and Solutions6.1 Cannot Open the Web Page6.2 Token Verification Failed6.3 No Response in Conversation or Model Loading Failed6.4 Allowed Address Configuration Not Effective
1. Course Content
Course Overview
OpenClaw WebChat is a browser-based web interaction interface. Without installing any client software, you can simply enter the address in your computer browser to have conversations with the robot. This course will detail how to interact with OpenClaw through WebChat.
Learning Objectives
- Learn how to configure the allowed addresses (Allowed Origins) for WebChat
- Master the method of entering the OpenClaw Web UI through a browser
- Be able to switch models and have conversations in the web interface
- Understand common problems and solutions when using WebChat
2. Add Allowed Addresses
- Set the address whitelist that can access WebChat in the OpenClaw configuration file:
nano $HOME/.openclaw/openclaw.json# Or use your preferred editor, such as vim, code, etc.- Locate the
gateway.controlUi.allowedOriginsconfiguration item and fill in the vehicle computer IP address +:18789 - If your vehicle computer has multiple IPs, separate them with commas

- Save and exit press
Ctrl+Oto save andCtrl+Xto exit (nano editor) - Restart the gateway to apply the configuration
xxxxxxxxxxopenclaw gateway restart3. Enter the Web UI
- On a computer on the same network segment as the vehicle computer, open a browser (regardless of operating system), enter
vehicle IP:18789in the address bar, and the page will jump to the gateway dashboard interface - Enter
yahboomin the gateway token box, then click Connect directly

- After that, you enter the OpenClaw web interface, where you can have conversations with OpenClaw, monitor, and configure parameters, etc.

4. Model Switching and Conversation
- In the model selection box at the top of the web interface, you can select a configured model to temporarily switch the model of the current session

- After selecting a model, you can have conversations with OpenClaw in the dialog box

5. Common Session Commands
In the WebChat dialog box, besides typing text directly to talk with OpenClaw, you can also use slash commands starting with / to perform various operations. Here are some common session commands:
| Command | Function | Usage Example |
|---|---|---|
/model [model name] | Switch the model of the current session | /model gpt-4o |
/stop | Abort the reply currently being generated | Type /stop directly |
/new | Start a new session (clear the current conversation history) | Type /new directly |
/reset | Reset the current session (alias for /new) | Type /reset directly |
/compact | Compress the session context to save tokens | /compact |
/fast [on/off] | Toggle fast mode (disable thinking chain output) | /fast on |
/status | View the current running status and execution information | Type /status directly |
/help | Show brief help information | Type /help directly |
/commands | View the full catalog of all available commands | Type /commands directly |
/think [level] | Set the output level of the thinking chain | /think off |
Tip: Slash commands must be sent as a standalone message (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
Symptom: After entering the address in the browser, it prompts that the page cannot be accessed or the connection times out.
- Vehicle computer gateway not running — Make sure the OpenClaw Gateway is started, and run
openclaw gateway statusto check the status - Network is not reachable — Confirm that the computer and the vehicle computer are on the same LAN, and use
ping vehicle-IPto test connectivity
6.2 Token Verification Failed
Symptom: After entering the token, it prompts authentication failure and cannot connect.
- Token entered incorrectly — Make sure
yahboomis entered in the token box (pay attention to case) - Token configuration was modified — Check whether the value of the
gateway.controlUi.authTokenconfiguration item inopenclaw.jsonmatches what you entered
6.3 No Response in Conversation or Model Loading Failed
Symptom: Successfully entered the web interface, but OpenClaw did not reply after sending a message.
Possible causes and solutions:
- Model not configured correctly — Run
openclaw models listandopenclaw models statusin the terminal to check whether the model is configured and available - API-KEY not set or expired — Refer to the API-KEY configuration section to reconfigure
- Model switching error — Try using the
/modelcommand in the dialog box to reselect a model - Gateway connection disconnected — Restart the gateway:
openclaw gateway restart
6.4 Allowed Address Configuration Not Effective
Symptom: allowedOrigins has been filled in but still cannot be accessed.
Possible causes and solutions:
- Gateway not restarted — After modifying the configuration file, you must run
openclaw gateway restartfor it to take effect - IP address entered incorrectly — Use
ip aorifconfigto confirm the actual IP address of the vehicle computer - Configuration item in the wrong location — Confirm that
allowedOriginsis under thegateway.controlUinode, not in another location