The Tunnels and Webhooks screens list every session on your account, whether it was created in the app, in a terminal, or by an agent. Each row shows live status, traffic, and spend. The creation sheet covers what the CLI flags do, so you can build anything from the app.
Creating endpoints#
A new webhook can start with a custom response (status, body, headers, delay, and match rules or a script), signature verification with any of the 16 provider presets or a generic HMAC scheme, an email inbox, forwards, email notifications, and local delivery to a port or command on this Mac. Webhooks default to running until you stop them, with 24-hour, 3-day, and 7-day auto-stop options.
A new tunnel takes a port, an optional stable subdomain, optional Basic auth, and an auto-stop time of 1 hour, 8 hours (the default), 24 hours, or 3 days. Each option shows what it would cost. If you turn auto-stop off, the sheet warns you that the tunnel will bill until you stop it.
Editing live#
You can edit an endpoint while it runs: change the response, rotate a verification secret, or add a forward. Changes apply immediately, without a restart. This works on CLI-started sessions too, which makes the app the quickest way to reconfigure something an agent set up.
Ended sessions#
Stopped and expired sessions move to an Ended section with their captured traffic intact. The app keeps them for 7 days, up to 20 sessions, so you can still inspect what a finished test run received. You can restart an ended endpoint on its original URL.
Pulses#
The Pulses screen lists your scheduled calls and dead-man's switches with their run history, next to tunnels and webhooks.