OtterKit's servers answer webhooks on their own, and a tunnel is one CLI command, so nothing about the platform requires an app. The Mac app exists for two reasons: endpoints pile up faster than you can track them, and some protections only work from software that runs on your machine.
One live picture of everything#
A tunnel from this morning's terminal, a webhook an agent created during last week's test run, an endpoint you made in the console: they all belong to one account, but they started in different places. The app shows every session in one window with traffic streaming in live, whoever or whatever created it. It reads the same credentials and session records as the CLI, so there is nothing to connect or sync.
Your local ports, one click from a URL#
The dashboard lists what is listening on your Mac, such as a Vite dev server on :5173 or a worker on :8787, and puts an Expose button next to each. A browser tab can't see your ports. A native app can.
Guardrails that need to run locally#
Tunnels bill by the connected hour, and the classic mistake is the tunnel you forgot. The app stops tunnels when your Mac goes to sleep, since a sleeping Mac can't serve one anyway. It notifies you when a tunnel has been idle for hours, and it keeps a projected monthly spend in the menu bar. See Spend Guardrails for details.
Full configuration, not a read-only viewer#
Every setting the CLI takes at creation time is in the app: responses, verification, forwards, notifications, local delivery, and TTLs. You can edit them live, even on sessions your agents started from the terminal.