expose

Expose local dev servers to remote users via Tailscale with unique paths.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill expose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expose
Source: https://github.com/stevengonsalvez/nanoclaw-standalone/tree/main/container/skills/expose
Command: npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill expose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expose local services from a developer's workstation to remote users over Tailscale using unique, persistent paths, while preserving the root path of your main application.

Core Features & Use Cases

  • Expose a local service on a unique path via Tailscale, enabling secure remote access.
  • Preserve the root path for the main application to avoid conflicts.
  • Automatically detect running dev servers and expose them with auto-generated paths, plus provide both HTTPS and direct access URLs.
  • Track and manage exposed services locally for quick reference and cleanup.

Quick Start

Invoke /expose to auto-detect a running dev server and expose it with a unique Tailscale path.

Frequently Asked Questions about expose

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

FAQPage Schema
How do I expose a local dev server to remote users over Tailscale?

You can expose local dev servers over Tailscale by invoking the expose command, which auto-detects running services and generates unique, persistent paths for secure remote access. It provides both HTTPS and direct access URLs while recording mappings to a local registry.

Can I expose local services without altering the root path of my main application?

Yes, exposing local services without altering the root path is supported. The tool creates non-conflicting, unique paths for each exposed service, preserving the root path for your main application to avoid routing conflicts during development.

What is the best way to manage multiple exposed local services for testing?

The best way to manage multiple exposed local services is using a local registry file. The tool records all service mappings to this registry, enabling quick reference, tracking, and cleanup of active Tailscale exposures.

Do I need Tailscale to securely expose local services from my workstation?

Yes, Tailscale is required to securely expose local services from your workstation. It provides the network infrastructure for routing traffic to isolated container applications via unique paths and generating secure HTTPS URLs.

How does auto-detection work for local development servers?

Auto-detection works by scanning your local environment for active dev servers. Once detected, the tool automatically generates non-conflicting paths and exposes the services over Tailscale, providing both HTTPS and direct access URLs.

Why does exposing a containerized app break my root path routing?

Root path routing breaks when exposure tools override the main application path. This tool prevents that by assigning unique, persistent paths to each exposed service, ensuring the main application root path remains preserved and conflict-free.