Using the OpenClaw Web Control UI

The OpenClaw Web Control UI lets you manage your agent, channels, and configuration from a browser. This guide covers how to access it, typical login flow, and common tasks.

📘 Security: The Web UI should only be reachable over a secure channel. By default the Gateway binds to localhost; use a VPN or SSH tunnel for remote access. See Security Best Practices and Network Isolation.

Accessing the Web UI

  • Default URL - When the Gateway is running, the Web UI is often available at a local URL such as http://127.0.0.1:18789/ or the port shown in your config. Check your config or run openclaw status for the exact address.
  • Start the Gateway - If the UI does not load, ensure the Gateway is running (openclaw gateway start or your platform’s service). See Post-Installation Setup and Gateway Issues.
  • Remote access - Do not expose the UI directly to the internet. Use SSH port forwarding (e.g. ssh -L 18789:127.0.0.1:18789 user@your-server) or a VPN (e.g. Tailscale) and open the forwarded or VPN address in your browser.

Login and First Use

Depending on your OpenClaw version, the Web UI may require a token or no login when bound to localhost. If a token is required, it is usually generated during onboarding or found in your config directory. Check the official documentation for the current authentication method. After logging in, you should see a dashboard or home view with links to agents, channels, and settings.

Common Tasks in the Web UI

  • Add or edit channels - Configure Telegram, Discord, Slack, and other messaging platforms with tokens or OAuth. Equivalent to editing the channel section of your config; see Channel Setup for per-platform guides.
  • Manage agents - View or edit agent names, system prompts, and model assignments. See Agent Customization for concepts.
  • View status and logs - Check gateway and channel status, and sometimes recent logs. For deeper diagnostics use the CLI: openclaw doctor, openclaw logs.
  • Config and credentials - Some setups let you edit config or paste API keys in the UI. Prefer environment variables or secrets managers for production.

Exact screens and options depend on your OpenClaw version. Refer to the official docs and in-UI help for the latest layout.

When to Use CLI Instead

Some operations are easier or only possible from the CLI: openclaw doctor, openclaw config validate, openclaw gateway probe, and skill installation. Use the Web UI for day-to-day channel and agent management; use the CLI for troubleshooting and automation. See Quick Diagnostics and API Reference.

Related