Features

HarborClient is a desktop API client for building and sending HTTP requests, organizing saved work into collections and environments, and collaborating with teammates through shared storage and team hubs. Extensions add custom behavior and appearance, and built-in search helps you jump to any request, setting, or plugin from anywhere in the app.

Request builder

The request editor is the center of HarborClient. Choose an HTTP method, enter a URL, and configure query params, headers, body (none, JSON, or plain text), and authorization (None, Basic, Bearer, or OAuth 2.0 Client Credentials). Each request also has access to a per-host cookie jar for session management.

See Making requests for the full guide to editor tabs, variables, and sending.

Cookies

HarborClient persists cookies by hostname so sessions survive across requests. Edit cookies from the request editor's Cookies tab or manage every domain from File → Cookies. Responses that include Set-Cookie headers update the jar automatically.

See Cookies for jar behavior, domain management, and capture rules.

HTTP methods

HarborClient supports the standard HTTP verbs: GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS. The method selector sits beside the URL bar; body and certain editor tabs adjust automatically based on the method you choose.

See Making requests for method-specific behavior and keyboard shortcuts.

Response viewer

After you send a request, the response panel below the editor shows status code, timing, size, response headers, and body. JSON responses are pretty-printed for readability. The active tab's response is always what you see in the panel.

See Making requests for copying, formatting, and inspecting responses.

Snippets

HarborClient stores reusable JavaScript blocks in an app-wide snippet library under File → Snippets. Reference a snippet from any collection or request PreRequest or PostRequest script list with Snippet library... instead of duplicating code. Snippet rows are live pointers — editing the library updates every request that references them on the next send.

Chain multiple steps in a single request stage by adding several scripts to the same list: mix inline scripts and snippet references, drag to reorder, and enable or disable individual rows. Scripts run top to bottom (up to 64 per request stage), and variables or request changes from earlier steps are available to later ones. Collection scripts run before request scripts in each request stage.

See Request scripts for the hc API, execution order, and script limits, and Using snippets for the snippet marketplace and library management.

Collections

Collections are named groups of saved HTTP requests. Create, rename, and delete collections from the sidebar; organize requests into folders and inherit shared variables, headers, authorization, and script lists at the collection level.

See Collections for the sidebar guide, folders, and collection settings.

Storage locations

Collections, requests, and environments live in pluggable storage locations. Use SQLite locally or connect to remote engines such as Firestore, MySQL, or PostgreSQL. You can even use Git. Each location is configured independently under Settings → Storage.

See Storage for why remote storage matters, storage types, and how to assign collections and other data to specific locations. See Settings for connection field reference.

Team Hub

Connect HarborClient to a self-hosted HarborClient Team Hub instance for token-based shared collections without manual storage setup for every teammate. Hub connections appear alongside local and remote storage locations in the sidebar.

See Team Hub for setup, user management, and sync behavior.

Team collaboration

Point multiple HarborClient instances at the same remote storage location to share collections and saved requests across your team. Sidebar environments stay local on each machine. For live remote collections, signed and encrypted share tokens use RSA keys you manage under File → Sharing Keys.

See Storage for collaboration options and Sharing Keys for identity, trusted keys, and collection shares.

AI assistant

Chat with OpenAI, Claude, or Google Gemini using your own API keys — or use models provided by a connected Team Hub. The assistant can inspect collections, send requests, read responses, and query JSON bodies with JMESPath.

See AI assistant for provider setup, model selection, and tool behavior.

Plugins

Extend HarborClient with installable .hcp packages or load unpacked plugins during development. Plugins can add custom settings panels, HTTP hooks, sidebar panels, and persistent storage. Browse the plugin marketplace or manage installs under File → Plugins.

See Using plugins for installation and Plugin development for building plugins.

Themes

Install appearance themes as plugin packages with categories: ["themes"] in the manifest. Themes use the same marketplace and install flow as plugins, managed under File → Themes.

Browse the theme marketplace or see Using themes to install and manage themes.

Search and actions

Jump to collections, requests, environments, settings, plugins, and themes from the global Action menu (Cmd/Ctrl+Shift+P). Filter in place with sidebar search, settings search, and marketplace or installed search on the Plugins and Themes pages.

See Action menu for global navigation and commands, and Search for focused search surfaces.