What is the WebChat URL?

WebChat is available at http://localhost:3000 as soon as the OpenClaw Gateway is running. It's a browser-based chat interface built into OpenClaw — no extra installation, no account, no configuration. Open it in any browser on the same machine where OpenClaw is installed.

Can I use WebChat on my phone or other devices?

Not directly — WebChat only listens on localhost (your own machine). Other devices on your network can't reach it without additional configuration. For mobile access, connect a proper channel like Telegram or iMessage instead. Those channels work from any device anywhere.

Does WebChat remember my previous conversations?

No — each time you open WebChat, it starts a fresh session with no memory of previous chats. For persistent memory across sessions, configure MEMORY.md as covered in Module 5. MEMORY.md persists facts between sessions regardless of which channel you use, including WebChat.

WebChat – HowOpenClaw

WebChat is the built-in browser interface for OpenClaw. It requires no installation, no configuration, no accounts. If the gateway is running, WebChat is available.

Access it at: http://localhost:3000

When to Use WebChat

Initial Verification

Before connecting any external channels, verify your agent works. Send test messages through WebChat to confirm:

Your SOUL.md personality is configured correctly
Skills are installed and responding
The AI model connection is working
Memory and context are behaving as expected

If something's wrong, you want to catch it here — not after you've connected iMessage or Slack.

Development and Testing

When you're modifying SOUL.md, installing new skills, or iterating on configuration, WebChat lets you test changes without affecting your live channels.

Change SOUL.md → restart gateway → test in WebChat → confirm behavior → then trust it on your real channels.

Local Access

Sometimes you just want to use your agent from your computer without switching to a messaging app. WebChat works for that.

Troubleshooting

If your agent is behaving unexpectedly on a channel, test the same query in WebChat. If it works in WebChat but not in the channel, the problem is channel-specific (configuration, permissions, routing). If it fails in both, the problem is the agent itself (SOUL.md, skills, model).

This isolation makes debugging much faster.

Technical Details

URL: http://localhost:3000
Conversation type: Single-user, single-session
Group support: Not available
Authentication: None (local access only)

WebChat only listens on localhost. It's not accessible from other devices on your network unless you've explicitly configured remote access.

Rich Output Display

WebChat now renders assistant media, replies, and voice directives as structured chat bubbles, making responses more visually organized and interactive.

Embedded Content

Your agent can embed rich media directly in messages using the [embed ...] tag:

[embed type="image" src="https://example.com/image.png" alt="Description"]
[embed type="video" src="https://example.com/video.mp4"]
[embed type="audio" src="https://example.com/audio.mp3"]
[embed type="link" href="https://example.com" title="Example Site"]

External Embed URL Security

By default, external embed URLs are gated behind config to prevent unwanted external resource loads. To enable external embeds, configure:

{
  "channels": {
    "webchat": {
      "allowExternalEmbeds": true
    }
  }
}

If disabled, only local and workspace-internal embeds are rendered. This is the recommended setting for privacy-conscious setups.

Ready to connect a real channel?

WebChat is for testing. When your agent is working correctly, connect an external channel:

Telegram — easiest external channel, works on iOS and Android
iMessage — native Messages app experience on iPhone (requires Mac)

Limitations

Single session only. WebChat doesn't support multiple concurrent conversations. If you close the browser and reopen it, you start a fresh session.

Local only. Can't use WebChat from your phone or other devices without additional configuration.

No persistent history. Conversation history isn't persisted between sessions in WebChat. For persistent memory, see Module 5: Memory & Personality.

No channel-specific behavior. MESSAGING.md routing rules don't apply in WebChat. It uses your default configuration directly.

WebChat not loading?

WebChat requires the gateway to be running. If http://localhost:3000 is unreachable, check that openclaw gateway is active. See the troubleshooting guide for gateway startup issues.