localtunnel

localtunnel creates a public URL that forwards requests to a port on your machine or another local host. It is mainly for testing callbacks, sharing in-progress local services, or giving external tools a temporary endpoint without deploying first.

• Expose a local dev server or webhook receiver on a public HTTPS URL for callback testing, demos, and remote QA.
• Request a named subdomain or point at a compatible custom tunnel server when you need a predictable endpoint or self-hosted relay.
• Proxy to a non-default local host or local HTTPS service and optionally print incoming request paths while the tunnel runs.

• The command surface is small and non-interactive once configured, so an agent can start a tunnel with a few flags and capture the emitted URL for follow-up steps.
• Automation has to parse stdout because the URL and request activity are plain text rather than structured JSON.
• Best for short-lived dev workflows where a skill can start the tunnel, hand the public URL to another system, then stop the process after verification.

• The default flow depends on the hosted localtunnel.me relay or another compatible server passed with --host.
• This CLI mainly opens and maintains a tunnel; it does not provide richer access controls, persistent resource management, or broad inspection commands.