CLI installs carry on into sign-in

Installing a CLI that needs an account no longer stops at the install. Hypergate now walks you into the account setup too.

Features

• CLI installs continue through account setup. When an in-app install finishes and the curated CLI still needs an account, Hypergate starts the vendor's sign-in or setup command itself, as long as that command can complete with a browser handoff and no terminal (az login, flyctl auth login, wrangler login). Commands that need an interactive terminal (gh auth login, aws configure, gcloud auth login, and similar) become an explicit next step: the exact command, why Hypergate cannot run it for you, and Copy. Installed rows keep this setup step visible instead of hiding it under Manage, and a successful setup says the CLI is ready to use.
• Agent-requested installs chain through setup too. Approving an install an agent asked for returns the tool's setup hint, and the app starts the follow-up sign-in job on its own.

Changes

• Nekko Agent naming. References to the sibling product now use its current name, Nekko Agent (formerly Kotrain and Agent Nekko), across the app, CLI output, the site and the docs. Its registry entry and command are now nekko-agent.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.26.0.tgz hypergated-1.26.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Homebrew installs finish in the app

Bug fixes

• Homebrew installs no longer stop after fetching dependencies. Homebrew 6 uses ask mode by default for install and reinstall, while Hypergate closes stdin for lifecycle jobs so an interactive process cannot hang. That combination could print the install plan, update dependencies, stop before pouring the requested formula, and still return exit code 0, so Hypergate reported success even though no CLI appeared.

  Hypergate now sets Homebrew's documented HOMEBREW_NO_ASK=1 only for daemon-spawned brew jobs. Install and Repair therefore complete without a terminal. The command shown in the app stays the same, other package managers are untouched, and hypergate cli install remains interactive when run in a terminal.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.25.0.tgz hypergated-1.25.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Search discovers native Homebrew routes

Bug fixes

• CLI search now discovers Homebrew routes generically. For the first few curated or npm results on macOS and Linux, Hypergate derives candidate formula names from the command and publisher, verifies the formula's status and homepage, and adds a noted Homebrew route when it matches; Windows and static catalog browsing are unchanged.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.24.0.tgz hypergated-1.24.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Deno and Bun install through Homebrew

Bug fixes

• Installing Deno or Bun ignored the Homebrew you already have. v1.17.0 taught Hypergate to rank a present system package manager above everything else, and it does. What it could not do is rank a route the catalog never listed, and these two tools carried only their vendor's curl … | bash script. So on a Mac with Homebrew sitting right there, Install piped a shell script into your home directory instead, and the tool that arrived had no upgrade or uninstall Hypergate could offer afterwards.

  Both now carry the Homebrew route their own docs publish: brew install deno, and for Bun the tap Oven documents, brew install oven-sh/bun/bun. Uninstall and Repair follow from it, so a Bun installed this way is removed by the tap path it came from rather than a formula that merely shares its name. The vendor script stays as the runner-up for a machine without Homebrew, and nothing changes on Windows or on a Mac that has no brew.

• Manage no longer offers to uninstall a tool with the wrong package manager. Giving Bun a Homebrew route had a side effect: for a Bun already installed by its own script into ~/.bun/bin, the Manage panel started defaulting to Homebrew and offering a brew uninstall that would never have found it. Where the installed path names no package manager the tool has a route for, Manage now prefers re-running the vendor's own installer, which is how those copies upgrade, and offers no uninstall. A tool you did install through Homebrew is unaffected and still manages through Homebrew.

Wrangler, Vercel and the Playwright CLI are deliberately still npm-only. Homebrew does package the first two, but neither Cloudflare nor Vercel documents that route, and a curated route says what the vendor says rather than what a repackaging happens to offer.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.23.0.tgz hypergated-1.23.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Building a release tells you when it cannot

Bug fixes

• Building the installers locally failed with an unreadable error. On a machine whose Node came from Homebrew, npm run build:installers died with a bare stack trace and no message. The underlying reason is that Homebrew builds Node against shared libraries, which makes it unable to produce a single-file executable and, more importantly, unable to produce one that would run on anyone else's machine.

  The build now checks for both problems before it starts, uses an official Node automatically if one is installed (fnm, nvm, volta, asdf, or /usr/local/bin), and otherwise stops with an explanation and the fix. It also says outright that the Node version is not the problem, because "update Node" is the natural conclusion and the wrong one.

Published releases were never affected: CI has always built them with official Node.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.22.0.tgz hypergated-1.22.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Granting an agent a key asks you to confirm

New

• Approving a credential request now asks for your fingerprint, and the prompt says who is asking. When an agent requests one of your keys, approving it raises your system's confirmation prompt naming the agent and the credential: "Hypergate" is trying to grant Claude Code access to the credential "GITHUB_TOKEN". Handing a key to an agent is the one grant you make on something else's behalf, so it is worth a moment of proof that a person is actually at the keyboard.

  If your machine cannot ask, because it has no fingerprint reader or equivalent, approving still works exactly as it did before and Hypergate tells you it could not ask rather than pretending you confirmed. Refusing the prompt grants nothing and leaves the request waiting, so you can simply try again.

Improvements

• The confirmation prompts say what they are actually about. Revealing a value now reads reveal the value of "GITHUB_TOKEN" rather than a bare name.

Bug fixes

• The test suite no longer asks you to confirm anything. Running Hypergate's own feature smoke tests on a Mac could raise a real confirmation prompt, for a credential the test had just invented. The suite now runs with prompts disabled.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.21.0.tgz hypergated-1.21.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

The stdio gateway finishes connecting before it answers

Bug fixes

• hypergated --stdio could answer a request before it had finished attaching. It connected its stdio channel first and only then looked up the upstream tool list and reported which daemon it had attached to. A harness that acted on the first response and exited immediately could miss that report entirely.

  Everything that can fail, and everything worth logging, now happens before the stdio channel starts serving.

• A failure at exactly the wrong moment could leave two servers on one channel. If the tool lookup failed after the stdio channel was already connected, the proxy reported that it had not attached, and the fallback path connected a second stdio server to the same input. Both would have been reading the same stream. The reordering above makes that unreachable, since every failure is now handled before anything is connected.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.20.0.tgz hypergated-1.20.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Hypergate can see your tools again

Bug fixes

• A Hypergate started at login could not find anything you had installed. When macOS launches the app for you, no shell is involved, so the daemon inherits a bare PATH of /usr/bin:/bin:/usr/sbin:/sbin. Nothing from Homebrew, nvm, cargo or bun is on it. On one Mac that meant Hypergate detected 1 of 23 command-line tools when all 23 were present.

  Hypergate now asks your login shell for your real PATH when the one it inherited looks like the system stub, and falls back to the usual install directories if the shell cannot answer. Starting it from a terminal changes nothing and costs nothing.

• Three things were quietly wrong because of it. The CLI list under-reported what you have. Install routes offered the vendor's install script instead of Homebrew, because a brew that cannot be found is correctly ranked below one that can. And the clis_list tool was telling connected agents your machine had no node, npm or docker.

• Local MCP servers could not start. Managed stdio servers inherit the daemon's PATH, so anything launched with npx or uvx failed to spawn at all when the daemon was started at login. Remote servers were unaffected, which is why this could sit unnoticed.

• Login Items said "Nekko Labs LLC" with no icon. macOS had nothing tying the background item to Hypergate, so it fell back to naming the certificate the app is signed with. The login item now identifies itself as Hypergate, with the app's icon. Enabling start-at-login also applies changes immediately instead of waiting for the next login.

After updating

• If you already had start-at-login enabled, toggle it off and on once. The entry in System Settings is rewritten when it is enabled, so the corrected name and icon appear after that.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.19.0.tgz hypergated-1.19.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Tools keep their labels and safety hints through the gateway

Every tool behind Hypergate was arriving at your agent stripped of the metadata clients use to decide what needs your approval. This release fixes that and finishes the paperwork for listing Hypergate in Claude's own directories.

Bug fixes

• A read-only tool no longer looks dangerous to your client. The gateway rebuilt each proxied tool from its name, description and input schema alone, dropping the four other fields an MCP tool carries. Clients read readOnlyHint to decide whether a call can be auto-approved and destructiveHint to warn you before one, so every server behind Hypergate arrived unannotated: safe tools lost their auto-approval and destructive tools lost their warning. Titles, output schemas, icons and hints now all survive the hop.
• Hypergate's own credential tools say what they do. credentials_list, credential_env and credential_request now carry titles and behavioural hints. credential_env is deliberately not marked read-only: it hands back a live secret, and a client that treated it as read-only could dispense one of your keys without ever asking you.
• Building the extension works when Homebrew installed Node. npm run build:mcpb died with "could not find npm-cli.js" on a Mac where Homebrew keeps npm under the prefix and Node in a versioned Cellar directory.

New

• The Claude Desktop extension is signable and carries its icon. npm run build:mcpb -- --sign signs the bundle with a certificate you configure, --self-signed covers a local check, and the archive now bundles the same gate mark the site and the app use, so the install dialog and a directory listing both have an icon to show. Unsigned, Desktop still installs it behind an "unverified" warning.
• Hypergate can be published to the MCP registry. A server.json describes the hypergated package for mcp-publisher, and the two places the version appears there move with every other version in the repo, so a submission cannot be rejected for disagreeing with itself.
• Where Hypergate can be listed, written down. docs/listing-submissions.md covers the three directories that are open to a local-first gateway, what each needs, and why the remote Connectors Directory is not one of them: it accepts internet-hosted https:// servers only, and Hypergate serves your own machine.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.18.0.tgz hypergated-1.18.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Installs prefer your system package manager

Improvements

• Homebrew, winget and Scoop now come before npm. Installing a CLI picked whichever route the catalog happened to list first, which meant Claude Code installed through npm on a Mac that had Homebrew sitting right there. Routes are now ranked by what they are and by what this machine can actually run: a system package manager you have, then the vendor's own install script, then npm and friends, with anything whose launcher is missing sorted below all three. A system package manager wins because it is also the thing that will upgrade and remove the tool later.
• Claude Code gains the routes Anthropic documents. brew install --cask claude-code, winget install Anthropic.ClaudeCode, and the native install.sh, alongside the npm package it already had. Wrangler, Vercel and the Playwright CLI are unchanged, because their vendors document no system-manager route and Hypergate does not invent one.
• A Homebrew formula outranks an npm guess in search. Looking up a tool you do not have yet puts an exact Homebrew match above npm's relevance-ranked results.

New

• Vendor install scripts run in-app. curl … | bash and irm … | iex routes used to be printed for you to paste into a terminal yourself, which made Hypergate's advice for Bun, Deno, uv, Fly and Claude Code a dead end. They now install with the same live log every other route gets.

  This is the only command Hypergate runs through a shell, so it is gated three ways over: the command has to be byte-identical to one shipped in Hypergate's own catalog, it has to match one of the two documented script forms, and it has to fetch over https from a short allowlist of vendor hosts. Nothing typed into a search box, returned by a registry lookup, or requested by an agent can take this path. Everything else still runs as a plain argument list with no shell involved at all.

Bug fixes

• Uninstalling a Homebrew cask names the cask. brew install --cask claude-code derived brew uninstall claude-code, which asks Homebrew about a formula of that name rather than the cask that was installed. The flag is carried through to Uninstall and Repair.
• Bun's Windows install command asked for http. The curated PowerShell route was copied from Bun's docs as irm bun.sh/install.ps1, with no scheme. PowerShell resolves that over http and follows a redirect; it now names https:// explicitly.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.17.0.tgz hypergated-1.17.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.