Claw Relay
ReviewAudited by ClawScan on May 10, 2026.
Overview
This instruction-only skill is transparent, but it asks you to route a cloud AI agent’s traffic through your home IP, which is a high-impact network and identity change.
Install only if you intentionally want a VPS or AI agent to use your home IP. Use a dedicated machine if possible, restrict access with Tailscale ACLs, understand how to turn the exit node off, and avoid using it for activity that could harm your home network reputation or violate service terms.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or overly broad configuration could send more traffic than intended through the user’s home network.
The skill instructs the user to run privileged networking commands that turn a laptop into an exit node and route the VPS through it.
sudo tailscale up --advertise-exit-node ... sudo tailscale up --exit-node=<laptop-hostname-or-ip>
Run these commands only manually and intentionally; prefer a dedicated machine or tightly scoped routing, and document how to disable the exit node afterward.
External services may see the AI agent’s traffic as coming from the user’s home IP, which can affect account trust, abuse handling, or ISP/provider terms.
The user’s residential network identity is delegated to a cloud node running an AI agent.
The human's laptop becomes a Tailscale exit node, allowing the VPS to route traffic through it ... Traffic exits from this IP.
Use this only when you are comfortable taking responsibility for traffic from the VPS; restrict access with Tailscale ACLs and avoid sharing the exit node broadly.
The user is trusting the remote installer and their network path at install time.
The setup uses a remote shell installer. This is a common official Tailscale installation method, but it still executes downloaded code.
curl -fsSL https://tailscale.com/install.sh | sh
Prefer official package repositories where possible, verify the URL, and inspect or pin installation sources for production systems.
One laptop outage or misconfiguration can disrupt the cloud node and any services or agents running on it.
A single routing change affects all VPS traffic and can also impact VPS connectivity when the residential laptop is unavailable.
Once the exit node is set, all traffic from the VPS routes through the laptop automatically ... the VPS will lose internet access while the laptop is offline
Use monitoring, a dedicated exit node, ACLs, and explicit rollback commands before relying on this for production workloads.