HTTP Tunnels

Expose a local web server, API, or any HTTP service to the internet through your active session.

Starting a tunnel

Pass ports when starting a session:

taiku --tunnel 3000,8080

This prints a public URL for each port:

  tunnel: https://taiku.live/t/abc1234xyz/p/3000/
  tunnel: https://taiku.live/t/abc1234xyz/p/8080/

How it works

Requests to the tunnel URL are proxied through the server to your CLI, which makes the request to localhost:{port} and streams the response back.

A Service Worker is installed on first visit to rewrite paths and handle navigation seamlessly — your web app works as if it were served directly.

Port approval

Tunnel ports must be declared upfront with --tunnel. Session participants can request additional ports, but the host controls access:

• --open-tunnel — auto-approve all port requests
• Tunnel admin link — a separate URL that grants port approval rights without host confirmation
• Default — port requests are denied

Viewing tunnels

From within a session, tunnels can be opened as:

• Inline preview — a modal overlay inside the session UI
• Tiled pane — alongside terminals in the tiling layout
• New tab — open in a full browser window

All views support back/forward navigation and refresh.