# HarnessLink 17.5.55 release notes

5 changes, released Oct 8, 2026.

### Added

- Install and `superpi update` also link `harnesslink` and `hlk` to the same launcher as `superpi` (Windows: `harnesslink.cmd`, `hlk.cmd`); an `hlk` that belongs to another program is never replaced. Every `SUPERPI_*` environment variable can also be set as `HARNESSLINK_*`, which wins. Cloud calls send `User-Agent: harnesslink/<version>`.

### Changed

- The CLI says HarnessLink: every message, help text, setup screen and MCP tool description, with links to [https://harnesslink.sh](https://harnesslink.sh) and the design system's blue as its accent. The command is still `superpi` and data stays in `~/.superpi`.
- The cloud API base moves to [https://api.harnesslink.sh](https://api.harnesslink.sh). A `cloud.token` pinned to api.superpi.sh, api.superpi.app, superpi.sh or superpi.app is rewritten in place (atomically, still 0600) the first time the CLI or the service reads it; self-hosted bases are untouched. The installers and `superpi update` download from [https://harnesslink.sh](https://harnesslink.sh) by default; superpi.sh keeps working.
- Hooks, the omp extension, the MCP hub, `mcp register` status and the service supervisor recognise both the `superpi` and the future `harnesslink` names and still write `superpi`. Installing the service removes a `harnesslink`-named unit, so two services never compete for the gateway port.

### Fixed

- `superpi telegram` ignored the cloud URL override and the retired-domain rewrite; it now uses the same API base as every other cloud call.

Update HarnessLink and every installed harness to its current release:

hnl update

New machine? Install with:

curl -fsSL https://harnesslink.sh/install.sh | bash

[Newer: 17.5.56](https://harnesslink.sh/releases#v17.5.56) · [Older: 17.5.54](https://harnesslink.sh/releases/17.5.54) · [All releases](https://harnesslink.sh/releases) · [Atom feed](https://harnesslink.sh/releases.atom)