Command line
update
Check for and install the latest Vibrai release (CLI + MCP server + M4L device + Python remote script)
--check
Only report whether an update is available; make no changes.
--yes
Apply without the confirmation prompt (required for non-interactive use).
--force
Reinstall the latest release even if already up to date.
--rollback
Restore the previously installed CLI binary (and MCP server binary, if present) from backup.
MCP tools
update
Check for and optionally install the latest Vibrai release. By default (apply=false) this only reports whether an update is available. Pass apply=true to download + verify (SHA-256) + swap the vibrai CLI binary, swap the MCP server binary (Vibrai.Mcp) and refresh the Claude Desktop extension bundle (Vibrai.mcpb) when the release ships them, and reinstall the Max-for-Live device + Python remote script (via the same installer as install_device / install_vibrai_remote_script). If Ableton Live is running during an apply, M4L/Python changes take effect after you restart Live; if the MCP server was updated, restart Claude Desktop (or your MCP client) to use the new version. Returns the current/latest version, update_available, per-component status (cli, and mcp on platforms that ship an MCP server), and (on apply) the actions taken. Applying is destructive (swaps binaries); requires confirm=true (parity with the CLI’s vibrai update --yes); refuses without changing anything otherwise.
Apply the update (download + swap + reinstall). Default false = check only.
Reinstall even if already up to date (default false).
Roll back to the previously installed CLI binary and MCP server binary, if present (default false).
Confirm the binary swap (CLI —yes equivalent). Must be true when apply=true; confirm with the user first.