claw-relay for Openclaw

A networking skill that routes AI agent traffic through residential IPs using Tailscale exit nodes without custom proxy software.

nicholaslocascio
v1.0.0
Feb 27, 2026
1
889
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install claw-relay

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install claw-relay using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is claw-relay?

claw-relay is a streamlined methodology for routing AI agent traffic through a residential IP address by leveraging Tailscale exit nodes. This approach eliminates the need for custom relay code, daemons, or complex proxy software, instead utilizing the security and performance of the WireGuard protocol. By connecting a cloud-based VPS to a residential node, developers can ensure their AI agents operate with the reputation and accessibility of a home internet connection.

Integrating this into your Openclaw Skills allows for a transparent networking layer where the AI agent remains unaware of the underlying tunnel. All traffic from the cloud node is encrypted and passed through the residential node before hitting the public internet, making it appear as though the agent is physically located at the residential site. This is achieved entirely through standard Tailscale configurations, ensuring a stable and professional-grade connection for automated workflows.

claw-relay Use Cases

  • Bypassing data center IP restrictions when running agents on cloud providers like AWS or DigitalOcean.
  • Accessing geo-fenced services that require a specific residential location.
  • Enhancing privacy by masking the physical location of the AI agent server.
  • Maintaining high deliverability and success rates for web-based AI automation tasks.

How claw-relay Works

  1. The residential node (usually a laptop or home server) is configured as a Tailscale exit node.
  2. The cloud node (VPS running the AI agent) joins the same private Tailscale network.
  3. The cloud node is instructed to route all its outbound internet traffic through the residential exit node.
  4. All requests made by the AI agent on the VPS are tunneled via an encrypted WireGuard connection to the residential node.
  5. The residential node forwards the traffic to the internet using its home public IP address.

claw-relay Setup

Residential Node Setup

On your local machine, install Tailscale and advertise it as an exit node:

# macOS installation
brew install tailscale
# Enable exit node capability
sudo tailscale up --advertise-exit-node

After running this, go to the Tailscale admin console and approve the device as an exit node under 'Edit route settings'.

Cloud Node Setup

On the VPS running your agent, install Tailscale and set the exit node:

# Install Tailscale
curl -fsSL https://tailscale.com/install.sh | sh
# Connect to the residential exit node
sudo tailscale up --exit-node=<residential-node-ip>

Verify the setup by checking the public IP:

curl https://httpbin.org/ip

claw-relay Data Schema & Taxonomy

The claw-relay skill operates primarily at the network layer and does not generate complex local databases. It relies on the following configuration metadata:

Field Description
Exit Node IP The internal Tailscale IP (100.x.x.x) of the residential machine.
Tailnet Status The connectivity state between the cloud and residential nodes.
ACL Policy JSON-based access control lists defining which nodes can route traffic.
Machine Tags Metadata tags used to organize agents and exit nodes in larger deployments.

claw-relay Advanced Features

  • Support for Headscale for developers who require a fully self-hosted, open-source coordination server.
  • Tailscale ACL integration to restrict traffic routing to specific authorized agents.
  • Per-process traffic control using local proxies to route only specific agent tasks through the residential IP.
  • Zero-config agent support, allowing standard libraries like requests or fetch to work without proxy settings.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*