HarborClient is no longer only a desktop API client. Starting with the latest build, the same harborclient binary that opens the GUI also speaks the command line.

Pass nothing and you get the familiar app. Pass an HTTP method or run, and you get a CLI powered by the same engine as the GUI—shared HTTP stack, cookie jar, scripts, and collections.

Ad-hoc requests, HTTPie-style

Send one-off requests without leaving your terminal:

harborclient GET https://httpbin.org/get
harborclient POST https://httpbin.org/post --json '{"hello":"world"}'
harborclient GET https://httpbin.org/headers -H 'X-Token: secret' -v

Headers, JSON bodies, timeouts, verbose response headers, and optional TLS verification skips are all available. Help is one flag away: harborclient --help.

Run the collections you already built

The CLI reads the same local SQLite data as the desktop app. Run a saved collection by name or UUID:

harborclient run "My Collection"
harborclient run "My Collection" --stop-on-failure

Pre- and post-request scripts, the cookie jar, and script tests all run. Failed HTTP statuses, transport errors, or failing tests exit non-zero—so you can wire collection runs into local scripts and CI without a second toolchain.

One install, your data stays yours

There is no separate CLI package to chase. Install or update HarborClient, and the binary is ready for both modes. Collections and cookies live in the usual Electron userData directory on your machine—the same privacy model as the GUI.

Grab the latest release from harborclient.com or GitHub Releases, then try harborclient --help. Same harbor. New channel.