self-upgrade

Upgrade the Vellum assistant binary and restart gateway and assistant processes.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill self-upgrade-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-upgrade
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/self-upgrade
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill self-upgrade-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of keeping a local Vellum assistant and its gateway up to date without leaving the user unsure whether the processes are actually refreshed.

Core Features & Use Cases

  • Version-first upgrade workflow: captures the current vellum --version before making changes, so you can verify what changed afterward.
  • Deterministic upgrade and verification: installs vellum@latest, then re-checks vellum --version to confirm the upgrade took effect.
  • Safe restarts of gateway and assistant: restarts the gateway to pick up protocol/dependency changes and then uses vellum sleep/vellum wake so the updated assistant takes over cleanly.
  • Use Case: when you want to apply the latest fixes and improvements to your running autonomy setup, you can upgrade and ensure both the gateway and assistant are running the new version.

Quick Start

Run the self-upgrade skill to upgrade Vellum to the latest version, then restart the assistant and gateway while reporting the before/after versions and statuses.

Frequently Asked Questions about self-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely upgrade the Vellum assistant to the latest version?

To safely upgrade the Vellum assistant, record the current version, install vellum@latest, verify the new version, restart the gateway via SIGTERM, and restart the assistant using vellum sleep and vellum wake.

Why do I need to restart the gateway and assistant after a runtime upgrade?

Restarting the gateway and assistant after an upgrade ensures running services pick up protocol and dependency changes cleanly. The gateway restart applies updates, while vellum sleep and vellum wake cycle the assistant without manual coordination.

What is the best way to verify a Vellum assistant upgrade took effect?

The best way to verify a Vellum assistant upgrade is to capture the pre-upgrade vellum --version output, install vellum@latest, then re-check vellum --version to confirm the version changed successfully.

Does the Vellum upgrade process require manual process management?

The Vellum upgrade process minimizes manual process management by automating gateway restarts via SIGTERM if the gateway is found, and cycling the assistant with vellum sleep and vellum wake to ensure services pick up changes automatically.

What should I do if the Vellum gateway is not found during an upgrade?

If the Vellum gateway is not found during an upgrade, the self-upgrade workflow skips the SIGTERM gateway restart step and proceeds to restart the assistant using vellum sleep and vellum wake, reporting statuses and any errors encountered.

When do I need to run a self-upgrade for my service orchestration setup?

You need to run a self-upgrade during runtime maintenance when you want to apply the latest fixes and improvements to your autonomy setup, ensuring both the gateway and assistant processes run the updated Vellum version.