Updating Koyd

Update from the app

1. When a new release is available, an Update button appears in the workspace header. Settings → General → Updates shows the app and server versions and has Check for updates.
2. Choose Update, or Update Koyd in Settings. The dialog lists What's new in that release and explains the restart. Choose Update now, or Not now to keep working.
3. Koyd downloads and verifies the release. Progress appears in a banner at the top of the app.
4. Koyd backs up saved data, restarts the server on the new version, and checks that it started correctly. During the restart, the app says so and reconnects by itself.
5. The app reloads with the matching version. Drafts and pairings stay in place.

Good to know · Updating restarts the server and interrupts active work, including agent turns, terminals, and browser sessions. Finish or stop them first. Projects, sessions, and paired devices are kept. Keep the server computer awake. Wi-Fi sharing comes back after the restart only if Keep sharing after restarts and updates is on.

Other browsers and installed apps connected to the same server notice the new version and show their own Update button. That update reloads only the app, and server work keeps running. The same button appears when your browser has a newer app build ready. Other Koyd instances on the computer keep their current version until you restart them.

What is checked

The server accepts only a newer stable release built for its own operating system and processor. Before preparing it, Koyd verifies the publisher's Ed25519 signature, the download's signed size and SHA-256 checksum, safe archive paths, and every file against the release manifest.

The current version stays installed and in use until the new server passes its startup, identity, and version checks. Only then does the koyd command switch to the new version. If startup fails, Koyd restores the backup and starts the previous version.

Where one-click updates are available

One-click updates work for a per-user installation from the install command, running in the background through koyd start. Foreground (koyd serve), service-managed, portable, source, and custom-path setups update manually. For those, Settings → General explains why automatic updates are not available.

An older build without the updater needs one manual installation of a current release. An app hosted separately from the server gets its files from its own host, so updating the server cannot update that host.

Manual update

1. Let active work finish.
2. Run the install command again. It installs the new version beside the old one and keeps your settings, data, and paired devices. Running servers keep using their current files.
3. Restart the instance with koyd stop and koyd start.
4. Reload the app when it offers the new version.

irm https://koyd.app/cli/windows | iex
koyd stop
koyd start --open

For a service manager, stop the service, install the new release, and start it again through the manager with the same config and data folder.

If an update needs attention

A failed check or download leaves the running version untouched and removes the partial download. A download that stops responding times out. If a corporate firewall, VPN, or intercepting proxy such as Zscaler blocks it, the notice names that as the likely cause. Fix the problem, then choose Try again in the banner or in Settings → General.

Update errors show where update.log is on the server computer. It records each update step. Keep it: it is a history, not a lock, and deleting it does not help a retry.

If the server has not come back five minutes after the restart began, the app asks you to run koyd start on the server computer. That start finishes an interrupted update: if the new version never completed its checks, Koyd restores the full backup and starts the previous version. The app then shows the outcome, with Try again if the update did not complete.

Backups and copies of data from a failed start are kept for you to review. Recovery never deletes them, and Koyd never force-stops a server it cannot verify.

Disk space and retained versions

Allow room for the download, the unpacked release, the new installed version, and a complete copy of the data folder. Previous versions and update backups are kept and not cleaned up automatically. Remove them only after the update works and no running instance still uses them. Project folders outside the data folder are not part of the update backup.