Skip to content
Changelog v1.9.0 New Improved

The hookwatch CLI grows up

The hookwatch CLI now prompts for a workspace API key on first run, then opens a real tunnel to a local process and a live terminal dashboard.

Published 1 min read
On this page

The hookwatch CLI becomes usable end to end for a real workspace in this release. Previously it could open a tunnel and render a live dashboard, but there was no built-in way to authenticate; now the first run walks you through it.

Added

  • First-run API key prompt — running the CLI without a stored key shows a prompt screen that captures a workspace API key (hwk_…) and verifies it against the API before saving, so a bad key is caught up front rather than on first use. The same prompt appears the first time you start a tunnel.
  • Default server URL — the CLI ships with a sensible default server and rejects an invalid server URL before it ever asks for a key.

Improved

  • Key entry honours cancellation cleanly, and the prompt subtitle is mode-aware (plain setup versus tunnel setup) so it reads correctly in either entry point.

With a key in place, hookwatch tunnel forwards captured webhooks to a local process — so an external provider can reach a service on your laptop through a HookWatch endpoint — and a bare hookwatch run shows the live terminal dashboard. See the documentation for setup.

Notes

Release date comes from the v1.9.0 git tag (11 July 2026).

Get started

See what happened to every webhook.

HookWatch keeps the request, the response, and every attempt for each delivery — so the debugging, retry, and replay steps in this article are a matter of reading, not reconstructing.