Practical overview
When it fits
Use Crabwalk when you have an OpenClaw gateway and need a visual, real-time view of agent activity and tool-call sequences across messaging sessions.
Who it is for
- OpenClaw operators who want to observe agent sessions as they happen.
- Teams monitoring agent activity across WhatsApp, Telegram, Discord or Slack.
Documented uses
- View agent sessions and action chains in a live graph.
- Inspect tool-call arguments and payloads by expanding graph nodes.
- Filter sessions by platform and search by recipient.
Requirements & limits
The repository documents CLI, Docker and from-source options. It is public and licensed under MIT.
- Crabwalk depends on a running OpenClaw gateway and gateway authentication.
- Its monitor streams gateway activity over WebSocket.
- Docker users need to configure a gateway address reachable from the container; loopback-bound gateways require host networking according to the README.
- The README identifies TanStack Start, ReactFlow, Framer Motion, tRPC and TanStack DB in the application stack.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start Crabwalk from source
Set up the project from its repository and open the monitor locally.
Before you start
- An OpenClaw gateway running on the same machine
- A gateway authentication token
- Git and npm
Steps
Clone the Crabwalk repository and change into its directory.
Install dependencies with npm install.
Set CLAWDBOT_API_TOKEN to your gateway token and run npm run dev.
Open http://localhost:3000/monitor.
Expected outcome
The local monitor interface opens and can connect to the configured OpenClaw gateway.
Guide limitations
- The guide requires an OpenClaw gateway and a valid gateway token.
- The documented source setup is for a local development run; it does not describe a production deployment.
Run Crabwalk in Docker
Start the monitor container with a reachable OpenClaw gateway and workspace mount.
Before you start
- Docker
- A running OpenClaw gateway
- The gateway authentication token
- A workspace directory if workspace explorer access is needed
Steps
Run the documented Crabwalk image, publish port 3000, and set CLAWDBOT_API_TOKEN and CLAWDBOT_URL to the token and reachable gateway WebSocket URL.
Mount the host OpenClaw workspace at /root/.openclaw/workspace when workspace access is needed.
Open the monitor through the published port.
Expected outcome
The container runs Crabwalk connected to the specified gateway, with workspace files available when mounted.
Guide limitations
- The gateway generally runs on the host, so the container URL must reach it.
- For a loopback-bound gateway, the README calls for host networking rather than port mapping.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- crabwise-ai/crabwalk · Official homepage title · retained in its source language

