Separate the dashboard from the gateway
An Express backend connects to the OpenClaw gateway and relays status and events to browser clients over WebSocket.
Multi Agent System.
Make agent activity observable.
A real-time interface for agent health, sessions, memory, commands, and activity, backed by a WebSocket gateway connection.
01 / THE PROBLEM
The system challenge.
An agent running in the background needs an operational interface. Operators need connection state, session visibility, and a channel for commands and events.
02 / SYSTEM FLOW
Trace the architecture.
Select a stage to see its responsibility.Conceptual flow · based on the documented implementation
STAGE 01
The Next.js interface exposes agent health, sessions, memory, commands, and activity.
03 / IMPLEMENTATION
Decisions that matter.
The details that make this an engineering system.
Correlate asynchronous requests
Request IDs and a pending-request map match gateway responses to promises. Timeouts reject requests that do not complete.
Recover after disconnection
The gateway manager uses exponential reconnect backoff capped at 30 seconds. Pending requests are rejected when the connection closes.
A clear scope
This public dashboard demonstrates gateway integration and observability. It is distinct from the professional multi-agent orchestration work described in the resume.
04 / OUTCOME & EVIDENCE
What the work demonstrates.
Public source demonstrates request correlation, gateway event forwarding, session retrieval, and reconnect handling. No live deployment is claimed.
Review the implementation on GitHubCONTINUE EXPLORINGCrypto futures trading system
All selected work