update

Restart Vellum services and rebuild the macOS app with branch-aware git updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the hassle and risk of restarting the Vellum services and rebuilding the macOS app after switching branches, especially when you need predictable behavior on main vs feature branches.

Core Features & Use Cases

  • Restarts services cleanly: Captures a preflight snapshot, stops assistant and gateway processes, verifies they are down, and applies fallback cleanup if needed.
  • Smart branch-aware git handling: Defaults to pulling on main, skips git operations on feature branches to avoid unexpected changes, and supports explicit branch checkout or forced pulling.
  • Rebuilds and relaunches the macOS app: Runs the macOS build, starts the watcher process, and verifies health via a post-start process summary.

Quick Start

Run the update skill to restart Vellum and rebuild the macOS app, pulling from main when applicable.

Frequently Asked Questions about update

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

FAQPage Schema
How do I safely restart Vellum services and rebuild the macOS app after switching branches?

Restarting Vellum services safely involves capturing a preflight snapshot of processes, stopping the assistant and gateway, verifying they are down, and applying fallback cleanup before proceeding with git operations and a macOS app rebuild.

What is the best way to handle git branch updates when restarting local development environments?

Branch-aware git handling defaults to pulling updates on main, skips git operations on feature branches to prevent unexpected changes, and supports explicit branch checkout or forced pulling for predictable local development restarts.

Why does restarting Vellum require a preflight process capture and stop-and-verify shutdown?

Preflight process capture and stop-and-verify shutdown are required to confirm assistant and gateway processes are fully terminated, triggering fallback cleanup if needed to prevent conflicts during the macOS app rebuild and relaunch.

Do I need to run a dependency install every time I restart Vellum on a feature branch?

You do not need to run a dependency install when restarting Vellum on a feature branch, because dependency installs are conditional and only execute when git pulls actually occur during the update process.

Can I force a git pull or checkout a specific branch when restarting Vellum services?

Yes, you can force a git pull or checkout a specific branch when restarting Vellum services, overriding default branch-aware behavior to apply explicit updates before rebuilding the macOS app and verifying health.

What limitations exist when restarting Vellum on feature branches without pulling?

When restarting Vellum on feature branches without pulling, the process skips git operations and conditional dependency installs, leaving local changes untouched but deferring remote updates until an explicit pull is triggered.