harnsy

Updates

harnsy looks for a new release by itself and tells you; it installs nothing until you press «Update». The agents keep working while it updates.

What harnsy does on its own. A few minutes after it starts, and then once a day, harnsy reads the public list of releases on GitHub. The request carries only harnsy's version: no key, no machine ID; GitHub sees your IP address, as for any web request. When a newer one is there, Settings › Updates shows it, and the machine's button in the top bar gets a mark. Nothing is downloaded or installed before you say so. To stop the daily look, turn off «Look for updates» on that page; then harnsy asks GitHub only when you press «Check» or run harnsy update.

Update from the dashboard

  1. Open the dashboard on this machine: Settings › Updates. («Check for updates» in the machine's menu opens the same page and checks.)
  2. Read what is new, then press «Update» and confirm.
  3. The page shows the steps: «Download», «Check the signature», «Restart the node». The machine is away for a few seconds; agents in their terminals do not stop.
  4. The page reloads when the new version answers.

«Update» works only on this machine's own dashboard: not from a phone or a laptop signed in from outside, even with full control.

Before it replaces anything, harnsy makes a backup of the database (also when scheduled backups are off; see Backups) and checks the release's signature with keys built into your harnsy. A file that does not match is not installed: the page says «Signature mismatch» and nothing changes. If the new version does not come up, harnsy is built to put the old one back and tell you.

Update in a terminal

Shell
harnsy update --check      # this version, the latest release, whether it is newer
harnsy update              # download, check, ask, install and restart
harnsy update --rollback   # go back to the version the last update replaced

harnsy update asks before it installs; add --yes to skip the question. The tray app is not updated this way: run the installer again for it.

Stable or release candidates

«Channel» on the same page:

  • Stable — only releases.
  • Release candidates — also the trial builds that come out before a release, for those who try it early. The release itself then comes on the same channel. You can go back to «Stable» at any time.

In a terminal, harnsy update --rc takes a release candidate too.

Agents and updates

harnsy tells its agents to run harnsy update only when you ask. An agent's run may take only the latest stable release or a rollback: harnsy is built to refuse it a release candidate or a chosen version. If an agent runs it, your bell rings before anything is replaced («dev-1 is updating harnsy …»), and then shows how it ended: a failed or rolled-back update is red and asks you to check.

Several machines

With machines joined in a cluster, «Cluster machines» on Settings › Updates shows which version runs where. Each machine is updated on itself.

If something goes wrong

You seeUsually
«No connection to GitHub»the machine cannot reach github.com: check the network or the proxy (Settings › Reach from outside › Proxy)
«Signature mismatch»the download did not match the release's signature, so it was not installed. Try again; if it repeats, tell us
«Update failed»open «Log» on the page; try again, or run harnsy update in a terminal
no answer for 10 minuteslook at the bell and run harnsy update in a terminal

Questions? Ask on Discord →

Anthropic, Claude Code, OpenAI, ChatGPT, Codex, OpenCode, pi, Telegram, Discord, GitHub, Apple, macOS, iOS, iPhone, Safari, Google, Android, Chrome, Microsoft, Windows, Windows Security, Defender and QR Code are names of their owners’ products. harnsy is not affiliated with or endorsed by them. iOS is a trademark of Cisco used under licence by Apple; QR Code is a registered trademark of DENSO WAVE INCORPORATED. No logos.