Updating

bun run update

This rebuilds the desktop images, recreates the control container, and restarts running desktops. Volumes are kept — browser logins and extra installed packages survive.

Flags

Flag	Effect
`--pull-viking`	Also `docker pull` the OpenViking image before restarting.
`--dev`	Build a development desktop that can file product reports (see Product reports).

A later bun run update without --dev turns report filing back off; review still works.

What persists across updates

Docker volumes, including DATA_DIR (sqlite, media vault) and desktop home volumes.
Extra apt packages — the image build records them (record-apt.sh) and restores them on the next image (restore-apt.sh).
Browser profiles and logins on the desktop.

When you need an update

Seed content (skills, CLIs, AGENTS.md) is baked into the image and copied into desktops at start. After pulling changes to open-bot:

bun run images && bun run update

Existing desktops only see new seed skills, CLIs, and AGENTS.md changes after this.

Manifest or DB changes (plugins, voice, media vault...) need bun run db:generate for new tables, then the image rebuild + restart above.

Backups

The dashboard has a backup/restore flow (admin-configurable schedule and target) and per-desktop reset. See the configuration reference for the settings keys.