openclaw-integration

Integrate OpenClaw containers with the JAcoworks gateway for websocket bridging and event forwarding.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/fran0220/jacoworks --skill openclaw-integration-fran0220
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-integration
Source: https://github.com/fran0220/jacoworks/tree/main/.agents/skills/openclaw-integration
Command: npx skills add https://github.com/fran0220/jacoworks --skill openclaw-integration-fran0220

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, production-oriented integration path for using OpenClaw containers as cloud agent backends alongside local vm-agent instances, resolving handshake, routing, and event duplication issues between the gateway and webchat frontend.

Core Features & Use Cases

  • WebSocket Bridge: transparent proxying and bidirectional frame forwarding to support OpenClaw websocket handshakes and challenge-response authentication.
  • Container Dispatch & DB Migration: container_type routing, required database migration to add container_type, and example SQL for inserting OpenClaw container records.
  • Deployment & Frontend Compatibility: configuration guidance for openclaw.json (trustedProxies, control UI origins, device pairing) and webchat rebuild guidance to avoid duplicate agent/chat streams.
  • Use Case: deploy an OpenClaw container, register it in the DB with a reachable container_ip, confirm gateway handshake and streaming agent events for webchat.

Quick Start

Add an openclaw container record with container_ip set to the container's reachable IP, set openclaw.json trustedProxies and token, run the DB migration to add container_type, deploy the gateway, and rebuild and sync the webchat static files so the websocket bridge can handshake and stream agent events.

Frequently Asked Questions about openclaw-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a websocket bridge for container agent streaming?

The websocket bridge enables transparent proxying and bidirectional frame forwarding between the gateway and OpenClaw containers, supporting websocket handshakes and challenge-response authentication for cloud agent backends.

How do I add container_type routing to my database for OpenClaw deployment?

You must run a database migration to add the container_type column, then insert OpenClaw container records with a reachable container_ip to enable proper gateway dispatch and routing.

Does OpenClaw integration support staging and local test environments?

Yes, OpenClaw integration applies during container deployment, gateway configuration, webchat handshake validation, and debugging scenarios across production, staging, and local test environments.

Why does my webchat frontend receive duplicate agent streams after deployment?

Duplicate agent streams occur when front-end event parsing is not updated; you must rebuild and sync webchat static files to correctly parse events and eliminate duplicate agent or chat streams.

What trusted proxy and origin header settings do I need for OpenClaw gateway configuration?

You need to configure openclaw.json with trustedProxies, control UI origins, device pairing, and token settings, plus apply origin header rewriting and trusted proxy whitelisting for valid token-based handshakes.

Can I use OpenClaw containers as cloud agent backends alongside local vm-agent instances?

Yes, OpenClaw containers serve as cloud agent backends alongside local vm-agent instances, with the integration resolving handshake, routing, and event duplication issues between the gateway and webchat frontend.