Skip to main content
A Dev Tunnel gives your local application a stable public HTTPS endpoint. Tilde can use it to deliver ChatKit messages, webhooks, and tool invocations while you develop.

​
Open a tunnel

1

Install the OpenBot CLI

OpenBot owns Tilde authentication, state, tunnel, and plugin commands.
2

Sign in

Authenticate before opening the tunnel. The login flow opens Tilde and asks you to select a workspace.
Run pnpm exec openbot auth set-team later if you need to switch workspaces.
3

Run your application through the tunnel

Replace pnpm dev with your normal development command.
The CLI opens a managed Cloudflare tunnel, chooses an available local port, and passes that port to your process as PORT and TUNNEL_PORT. It prints the public tunnel origin when the connection is ready.
4

Test through Tilde

Keep the tunnel process running. Configure your local ChatKit agent with its endpoint path, then test it in ChatKit workspace.For a Next.js route at app/api/agent/route.ts, use api/agent as the local endpoint path in Tilde.
Signed endpoint wrappers such as chatKitEndpoint verify Tilde’s webhook signature before your agent code runs. Keep the signing key and other secrets on the server.
The tunnel exposes every page and API route served by your development process—not only the agent endpoint—to the public internet. Disable unneeded routes or protect them with authentication before opening the tunnel.
Stop the CLI process to close the tunnel. Replace the tunnel with your production endpoint before launch.