RosClaw for OpenClaw: Natural-Language ROS2 Robot Control from Messaging Apps
Connects OpenClaw to ROS2 robots through a plugin layer so operators can send natural-language commands from messaging apps and receive robot feedback in chat.
Tags
Target users
What it does
- Connects OpenClaw to ROS2 through a RosClaw plugin layer and
rosbridge_server. - Lets users control robots from WhatsApp, Telegram, Discord, or Slack instead of a dedicated robot console.
- Translates natural-language intent into ROS2 operations such as topic publish, service call, action goal, and camera snapshot.
- Returns robot feedback back to chat, keeping control and observation in the same messaging loop.
- Supports both simulation-first demos and real robot integrations through the same architecture._
Skills You Need
Pain Point
Most robot control stacks assume operators know ROS2 topics, services, and robot-specific interfaces. That works for robotics teams, but it slows down remote operation, cross-team collaboration, and quick experiments from non-ROS-native channels.
Core value of this case
RosClaw turns ROS2 control into a message-driven workflow. OpenClaw handles language, channel access, and tool orchestration; ROS2 keeps real-time robot interfaces and sensor systems. This makes robot control easier to access without replacing the existing ROS2 stack.
Typical scenarios
- Remote robot control from Telegram or Slack during demos, field tests, or internal operations.
- Fast simulation loops where a team wants to test movement, navigation, or sensor reads through plain language before building a richer UI.
- Cross-functional workflows where a non-robotics operator needs limited robot actions without learning ROS2 internals.
- Multi-channel robot access where the same robot can be reached through several messaging apps backed by one OpenClaw gateway.
How to setup
- Prepare Node.js 20+,
pnpm9+, and Docker. - Install dependencies and build the monorepo:
- Start the demo stack:
- Point your OpenClaw instance at the RosClaw plugin and configure the ROS bridge endpoint as
ws://localhost:9090. - Test commands such as moving forward, navigating to a room, checking battery state, or capturing a camera frame.
Related Links
FAQ
Does this only work with Telegram?
No. The repository describes WhatsApp, Telegram, Discord, and Slack as supported chat entry points.
Does RosClaw replace ROS2?
No. It sits between OpenClaw and ROS2, translating chat intent into ROS2 operations through the bridge layer.
Is there a non-LLM emergency stop?
Yes. The README documents /estop as an emergency stop path that bypasses AI.
Is the project API stable?
Not fully. The repository currently warns that it is undergoing a major re-architecture and migration to separate repos.