Tunnels & Webhooks in the App

The Tunnels and Webhooks screens list every session on your account — created from the app, any terminal, or by an agent — with live status, traffic, and spend. Creating one in the app has full parity with the CLI: everything you could pass as a flag is in the creation sheet.

Creating endpoints

A new webhook can be armed at creation with a custom response (status, body, headers, delay), signature verification against any of the 16 provider presets or a generic HMAC scheme, forwards, and email notifications. A new tunnel takes a port, an optional stable subdomain, and a TTL — the picker labels each option with what it costs, and never asks for explicit confirmation on tunnels.

Editing live

Endpoint configuration is editable while the session runs — change the response, rotate a verification secret, add a forward — and it applies immediately, without a restart. This works on CLI-started sessions too, which makes the app the fastest way to reconfigure something an agent provisioned.

Ended sessions

Stopped and expired sessions move to an Ended section with their captured traffic intact (kept for 7 days, up to 20 sessions), so you can still inspect what a finished test run received. An ended endpoint can be restarted on its original URL.