JamesWare · Dev tool

HookBench

Capture, inspect, forward, replay. Local-first webhook workbench.

Building CLI TypeScript Local-first

Not on npm yet Private repo

HookBench dashboard showing captured webhooks, a selected POST, and the JSON body

Problem

Vendors cannot POST to localhost. You often do not know what they actually send. Hosted catchers put those payloads on someone else’s dashboard.

What it does

One process: a URL, a live inspector, optional forward to your app, replay until the handler is right. Public tunnel only when you turn it on, with your ngrok token.

Why it exists

A developer instrument, not a webhook.site clone. Inspect + forward + replay, locally.

Look

HookBench dark dashboard with request list and JSON inspector — Dashboard

Capabilities

Catch what arrived, or proxy it to a local handler
Dashboard on :7331, ingress on :7332
Headers, query, body, raw, copy cURL, replay, compare
Ink TUI in the terminal, browser UI if you want it
Optional ngrok — your account, ingress only
History in .hookbench/ (gitignored)
Alias: hb

How it works

Runs on your machine. No JamesWare server. Tunnel is optional. Secrets stay local.

Current state

Usable locally. Private GitHub repo. Not published to npm yet. First loop is the 30-second demo: run it, POST JSON, see the request.

Get it

From the checkout, not a public install yet.

pnpm dev — dashboard at http://127.0.0.1:7331