Anonymous HTTP/WS tunnel. No login. No tokens.
Expose a local port to a public URL:
npx anontun 3000
The CLI prints a URL like https://anontun.example.com/t/<token>/. Anything you hit on that URL is proxied to http://localhost:3000 on the machine running the CLI. WebSockets supported. Tunnel dies when the CLI exits.
Behind an HTTPS-only proxy that blocks WebSocket upgrades (CI, agent sandboxes)? The CLI falls back to --transport sse automatically.
Source: github