Skip to content
Monitor entryAwaiting configuration

OpenClaw agent monitor

OpenClaw Office over a Cloudflare Tunnel for read-oriented monitoring of agent activity.

Awaiting configuration

Configuration entry

NEXT_PUBLIC_OPENCLAW_OFFICE_URL is not set. Add your Cloudflare Tunnel HTTPS URL and rebuild to embed the UI here.

After configuration, OpenClaw Office will appear in the monitor frame above.

Operating notes

This page embeds OpenClaw Office — the visual frontend for the OpenClaw multi-agent system — so you can follow agent activity in a read-oriented, “office floor plan” view.

How it is exposed safely

  • Cloudflare Tunnel terminates TLS and publishes a stable HTTPS URL. That matches what OpenClaw Office expects for browser features (for example crypto.subtle for device identity), which can fail on plain HTTP from a non-local host.
  • The tunnel should point at the host and port where you run OpenClaw Office (for example the default 5180 dev server or your production static server), not directly at arbitrary services you do not intend to expose.
  • Prefer additional access control on the tunnel (for example Cloudflare Access) if the URL could be discovered. Anyone who can load this page can see whatever the iframe is allowed to show.

What you need running

  1. OpenClaw Gateway on your machine or server (WebSocket endpoint; default is often ws://localhost:18789 — see OpenClaw docs).
  2. OpenClaw Office built or started (for example pnpm dev from source, or npx @ww-ai-lab/openclaw-office), with VITE_GATEWAY_URL / token configured per the project README.
  3. cloudflared (or Cloudflare Dashboard tunnel) forwarding HTTPS traffic to that Office HTTP port.

If the monitor area is not configured, set NEXT_PUBLIC_OPENCLAW_OFFICE_URL in your site’s environment to your tunnel URL (including https://) and redeploy. If the app sets X-Frame-Options or CSP frame-ancestors, use Open in new tab instead.