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
OpenClaw v2.0 update requires manual checks before installation
OpenClaw's latest update includes 12 breaking changes, a new plugin system, and 30+ security patches. The update will silently break setups if users run npm update without first checking environment variables, state directories, and browser automation configurations.
OpenClaw Memory Management: Complete Guide
Optimizing OpenClaw Setup: Practical Patterns and Insights
OpenClaw users share effective setup patterns, such as using cron for scheduled tasks and creating specialized sub-agents, to enhance functionality and cost-efficiency.
Practical fixes for OpenClaw reliability issues
A developer shares eight specific techniques that improved their OpenClaw setup, including a 3-tier memory system with daily logs and a knowledge graph, activation score management, and file-based rule enforcement.