KnockPort v0.4.1

KnockPort v0.4.1

Fixed

• Real-time tabs (WebSocket, SSE, MQTT, Socket.IO, GraphQL-WS) no longer show a persistent notice before connecting about the Local Agent not carrying a socket. These sessions always connect directly from the app, so the warning was noise that could not be dismissed or acted on. A short notice now appears only when a connection actually fails.

---

Unsigned build (not yet notarized or code-signed). Install with the one-line command on https://knockport.com, or clear quarantine after a direct download. Full source is attached below (FSL-1.1-ALv2).

KnockPort v0.4.0

KnockPort v0.4.0

Git, end to end

• Workspace-level source control: one git repository per workspace folder, with a Source Control view for the whole workspace, not just one collection.
• Initialize a git repository in place for any collection.
• Deleting a collection moves its folder to the OS Trash rather than erasing it.

Secret managers

• Connect HashiCorp Vault or 1Password Connect from Settings and resolve secrets at send time. Tokens live in the encrypted keychain, never in config.

Real-time as first-class requests

• WebSocket, SSE, MQTT, Socket.IO and GraphQL-WS connections are savable requests that round-trip in a collection and run inside a collection run.

Polish

• Nested submenus in the sidebar, a resize handle between the sidebar and the response view, and more even spacing across the analytics cards.
• Per-workspace tabs: each workspace remembers its own open tabs.

---

Unsigned build (not yet notarized or code-signed). Install with the one-line command on https://knockport.com, or clear quarantine after a direct download. Full source is attached below (FSL-1.1-ALv2).

KnockPort v0.3.8

KnockPort v0.3.8

• Scratch tabs restore silently. The restore notice now appears only when the saved request it belonged to was deleted since your last session.
• Free tier labelled "Free" (previously "Lite") throughout the app.
• New Privacy setting at the very bottom of Settings to turn off the anonymous install-count ping.

Ships source-available under FSL-1.1-ALv2 (future license Apache-2.0). The full source for this release is attached as KnockPort-0.3.8-source.tar.gz.

Install

• macOS / Linux: curl -fsSL https://knockport.com/install.sh | sh
• Windows: curl.exe -fsSL https://knockport.com/install.ps1 | powershell -NoProfile -ExecutionPolicy Bypass -Command -
• Or via Homebrew, Scoop, winget, or the direct downloads below.

KnockPort v0.3.7

Desktop builds for macOS (Apple silicon and Intel), Windows and Linux.

Source-available under the Functional Source License (FSL-1.1-ALv2; each release converts to the Apache License 2.0 two years after its date) — see KnockPort-0.3.7-source.tar.gz.

KnockPort v0.3.6

Highlights

Collections stop silently duplicating. Creating or renaming a collection onto a name that already exists in the workspace now prompts you to rename it — the same rule requests and folders already follow — instead of quietly keeping two and failing to write one later. Imports still de-duplicate automatically.

You stay signed in. The desktop app now holds and spends its refresh token, renewing silently on launch instead of dropping you back to Lite when the short-lived token expires. Open it after days away and you're still signed in.

---

First release since v0.3.3, so it also carries v0.3.4 / v0.3.5 (never published): collections and environments become plain files on disk under a folder you choose, and duplicate request/folder filenames are auto-suffixed on import rather than failing the migration.

KnockPort v0.3.3

Two Windows bugs. Both had been there since the platform shipped, and neither could appear on macOS.

Fixed

• After an update, Windows kept running the previous release. Not a stale version number — the whole previous build, working normally, until the page was refreshed by hand. The desktop app had been registering the web build's service worker inside itself, and that worker caches assets for the life of a build, so it went on serving the old release to the new binary.

  The registration was gated on the page's protocol being http(s), which reads as "only on the web" and is correct on macOS and Linux, where Tauri serves tauri://. Windows serves http://tauri.localhost, so the guard passed.

  0.3.2 and earlier cannot repair themselves — the frontend that would run the fix is the stale one. So this release evicts the worker from the shell, before any page code runs. Updating to 0.3.3 is what unsticks a Windows install; nothing needs to be done by hand.

• The "You're signed in" page never arrived on Windows. The browser showed "This site can't be reached" on the callback URL while the app signed in perfectly. The request was read and answered, but the socket was then closed with the rest of the request still unread — an abortive close, which sends RST instead of FIN, and a browser that receives RST discards the response it has already read. Windows enforces that; macOS and Linux do not.

Also

• The app now checks that the running binary and the loaded interface agree on the version, and reloads once if they do not. A disagreeing version number was the only outward sign of the first bug, and it took a user noticing it.

KnockPort v0.3.2

Added

• A console for collection runs. Scripts could always print; a run had nowhere to show it. Each request in the results now has its own Console tab, and the run as a whole has a Collection Console under both panes — every console.log, console.warn and console.error in the order they ran, with a filter that matches the request name as well as the message. Across thirty requests and five iterations, finding which one printed something was not a question you could answer by opening tabs.

• The runner's panes resize. Drag the divider between the results list and the response, or the top edge of the Collection Console. Double-click a divider to put it back where it was.

Changed

• Desktop history is kept in a database rather than the webview's storage. It survives the things an uninstaller leaves behind, and reading the last ten entries no longer means loading all of them. Existing history moves across on first launch. Nothing changes for the browser build.

Fixed

• The runner's Response tab formats the body again. The same JSON that gets syntax highlighting, line numbers and folding on an ordinary request was rendered as a flat block after a run. It now uses the same viewer.

• The Collection Console is visible before a run, not only after one. It was hidden on the configuration screen — which is the screen you are on when you open the runner.

KnockPort v0.3.1

Run a collection straight from its own context menu, and load runner data from a CSV or JSON file you upload rather than only from a connected folder.

Also fixes install counting: 0.3.0 recorded a ping the server had refused, so an install whose first launch met an error was never counted and never retried.

Desktop builds for macOS (Apple silicon and Intel), Windows and Linux.

KnockPort v0.3.0

Report a problem or ask for a feature from inside the app, see what you have filed and what happened to it, and keep that list when the app is reinstalled.

Desktop builds for macOS (Apple silicon and Intel), Windows and Linux.

KnockPort 0.2.1

Changed

• An available update no longer looks like an error. Every notice in Settings was red with a warning triangle, so "version 0.2.1 is available" was indistinguishable from "this build can no longer send requests". Red is now reserved for a build that has actually stopped working; an update is informational, and becomes a warning only once an enforcement date is attached to it. Screen readers get the same distinction — an update is announced without interrupting what you were reading.

• Release notes open in a dialog, with the install button in it. They used to sit open underneath the section, pushing everything below them off the page. View changes now opens them in their own window alongside Install and restart, so deciding and acting happen in one place. The install button on the Settings page is unchanged, for when you would rather not read a changelog first.

Fixed

• Install counting is desktop-only and far more accurate. The counter was reachable from the web app and from development builds, where every fresh browser profile looked like a brand-new machine — so the numbers counted page visits as installs. It now reports only from a released desktop build.

• Your install is no longer recounted after a reinstall. The identifier lived in the webview's storage, so clearing app data or reinstalling minted a new one and counted you twice. It lives outside that storage now. It is still a random id with no relationship to your machine or your account, and existing installs keep the number they already had.

• The platform a build reports is the real one. macOS installs were all recorded as Apple silicon regardless of the actual chip, because the check matched the browser engine's name (AppleWebKit) rather than the architecture. The desktop now reports its own build target.