Skip to content

Hypergate can see your tools again

Choose a tag to compare

@github-actions github-actions released this 26 Aug 11:53
· 12 commits to main since this release
68c24ff

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.