Skip to content
Docs0.9GitHubInstall

Running itUpgrade

Upgrade

Move an install to a newer Vendetta and restart what still runs the old code.

How to bring an existing install up to date, for whoever administers it. An upgrade is a pull and a rerun of the installer, then a restart of the processes that keep old code in memory. Changelog says what each release contains.

In your checkout:

git pull
bash install.sh

install.sh rebuilds and replaces the binaries in ~/.local/bin, rebuilds the web client, reinstalls the agent skills and each provider’s integration, and restarts the scheduler. On macOS it restarts the worker too. Your config.toml and prompt files are left as they are.

vendetta notify stop && vendetta notify start

If a systemd user unit runs the worker, restart that instead, since a stopped worker would be started again by the unit:

systemctl --user restart vendetta-notify.service

Plugins restart with the worker. Agents keep running.

Provider After an upgrade
Claude Code Restart Claude and resume. Idle sessions may also reload the Mod by themselves.
omp Restart omp and resume. /reload does not reload extensions.
OpenCode Restart OpenCode.
Codex, Gemini CLI Nothing. Their hooks use the new binary on their next event.

After you deploy, write people’s config again and restart their workers:

vendetta instance update

A project machine uses the image that matches your install. install.sh records which one from a clean checkout; if the published image is not that one yet, Vendetta says which commit it is and stops. Then either wait and refresh, or build it locally:

vendetta machine image refresh
vendetta machine image build --local

An install from an unpushed commit or with uncommitted changes always needs the local build.

vendetta --version
vendetta config check
vendetta notify status

notify status lists each plugin’s state. One that stays unavailable logs why; see Troubleshooting.