Upgrade

Upgrading is just re-running the installer — it detects the existing copy and lays the latest version over it. Sign-in, config, and history are always kept.

Agent

macOS / Linux

curl -fsSL https://16co.de/install_agent.sh | sh

Windows

irm https://16co.de/install_agent.ps1 | iex

On macOS the running app is quit, replaced, and relaunched automatically. On Linux the package upgrades in place and the service restarts. Your binding in ~/.code is untouched — no need to sign in again.

Server

Installed with the script or a package:

curl -fsSL https://16co.de/install_server.sh | sudo bash

(Or install the new deb/rpm by hand: sudo dpkg -i code-server_*.deb / sudo rpm -U code-server-*.rpm.) Your edited /etc/code.yaml is preserved by the package on upgrade; data, history, and certificates live in /var/lib/code and are untouched. The service restarts with the new version — browsers and agents reconnect within seconds.

Docker / Podman:

podman pull ghcr.io/yinyue123/16code:latest
podman restart code-server

Order & compatibility

There's no strict order, but upgrading the server first, then agents is the safe habit. Agent and server versions are meant to interoperate across minor releases; check the release notes for anything flagged breaking.