Custom Command Center App for OpenClaw: React PWA with WebSocket Proxy and Tailscale
A Reddit user (Weird_Night_2176) shared their custom command center app built on top of their OpenClaw gateway. The app replaces their previous WhatsApp-based control method, which was limited by Twilio's 50 messages/day sandbox cap. The setup runs on a Jetson device, serving a React PWA accessible anywhere via Tailscale.
Architecture & Key Components
- WebSocket Proxy: OpenClaw binds to loopback only, so the developer created a lightweight Express proxy server that bridges the WebSocket connection. This allows the React frontend to communicate with the OpenClaw gateway from any device on the Tailscale mesh.
- Frontend: A React Progressive Web App (PWA) served directly from the Jetson.
- Network: Tailscale mesh for secure remote access; the app works on iPhone via Tailscale.
Features of the Command Center
- Live Chat Interface: Direct chat with the AI agent "Bosefus".
- Agent Dashboard: Shows 14 agents with their last task and status.
- Trading Desk: Live Alpaca positions and crypto P&L.
- Crew Run History: Every automated job logged by name.
- Ollama Model Status: Live status from the Orange Pi model server.
- Build Fund Tracker: Tracks savings toward the next hardware upgrade.
- Push Notifications: Replaces WhatsApp for alerts.
Who This Is For
Developers running OpenClaw as an AI agent gateway who need a purpose-built UI beyond command-line or third-party messaging apps, especially those with multiple agents and trading integrations.
Resources
The user mentioned a full build walkthrough coming on YouTube. For now, the Reddit post has details on the architecture and motivation.
📖 Read the full source: r/openclaw
👀 See Also
Run OpenClaw with a Local LLM on macOS – Guide for 16–24GB RAM
A practical guide to setting up a quantized Qwen 3.5 model with OpenClaw on macOS (16–24GB RAM), including a test skill for verification.
Claude Code v2.1.36: Fast Mode Now Available for Opus 4.6
Anthropic releases Claude Code v2.1.36 with Fast Mode support for the latest Opus 4.6 model, enabling significantly faster code generation and analysis.
Fixing OpenClaw Agent Autonomy Issues: Skill Files, Tool Selection, and Cron Setup
A developer shares solutions for OpenClaw agents that stop working autonomously after initial setup. Key fixes include using external skill files instead of chat instructions, replacing browser tools with API-based tools or Puppeteer scripts, and properly configuring cron jobs.
Debugging OpenClaw + Ollama Local Model Timeouts: Five Fixes for Silent Failures
A developer identified five root causes for OpenClaw agents silently timing out with local Ollama models like Gemma 4 26B, including a blocking slug generator, a 38K character system prompt, and hidden timeouts. The fixes involve disabling hooks, modifying configs, and adjusting Ollama settings.