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>.

The CLI says HarnessLink: every message, help text, setup screen and MCP tool description, with links to 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. 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 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.

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

Flag notifications