remote-relay

What This Skill Does

The PrivateBridge skill (remote-relay) transforms your local OpenClaw instance into a managed, secure remote node. Instead of punching holes in your firewall with SSH or relying on insecure, third-party messaging apps like Discord or Telegram, this skill establishes an outbound-only WebSocket tunnel. By registering your agent with a relay server, you gain the ability to trigger workflows, chat with your agent, and perform health checks from anywhere in the world, all while keeping your local machine completely locked down from inbound traffic. It effectively bridges the gap between a private, secure environment and the need for remote accessibility.

Installation

To integrate the PrivateBridge skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/jason-czar/private-bridge

After installation, locate your configuration file and ensure you have provided the required relay_url, node_id, and auth_token fields. Once configured, restart your OpenClaw instance to initialize the secure WebSocket connection.

Use Cases

• Secure Remote Management: Control your home lab or office workstations without opening ports or exposing SSH.
• Deployment Monitoring: Monitor uptime and system health of distributed AI agent instances from a centralized dashboard.
• Automated Workflow Orchestration: Trigger complex tasks or specific workflows remotely based on events occurring outside your local network.
• Corporate Security Compliance: Maintain strict network perimeter security while still enabling remote interaction with internal AI tools.

Example Prompts

1. "PrivateBridge, execute the 'weekly-backup' workflow immediately and report status."
2. "Get the current health status and uptime for node-id 'lab-station-01'."
3. "Restart the OpenClaw service on the remote node gracefully after the current task finishes."

Tips & Limitations

• Exponential Backoff: The skill is designed for resilience; if the connection drops, it will wait longer between each successive attempt to reconnect, saving resources.
• Security Scope: Remote commands are restricted strictly to the defined capabilities. The skill does not provide shell access, ensuring that even if your relay auth-token is compromised, attackers are limited to OpenClaw-specific tasks.
• State Awareness: Remember that commands sent while the node is in 'Reconnecting' status are discarded. Always check node status before triggering time-sensitive workflows.