ha-self-update

Check and install Hope Agent updates via conversation with user confirmation.

1.4k|129|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/shiwenwen/hope-agent --skill ha-self-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ha-self-update
Source: https://github.com/shiwenwen/hope-agent/tree/main/skills/ha-self-update
Command: npx skills add https://github.com/shiwenwen/hope-agent --skill ha-self-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you keep Hope Agent up to date by checking for newer releases and installing them through the conversation flow, while preventing risky silent upgrades.

Core Features & Use Cases

  • Release-aware update checks: Runs an update check and surfaces the current vs latest version plus relevant release notes when an upgrade is available.
  • Guardrailed, confirmation-first upgrades: Uses user-confirmation gating for both install and rollback, never bypassing the Yes/No dialog.
  • Multi-formfactor support: Works across the desktop GUI bundle, the hope-agent server daemon installed via common package managers, and headless/self-contained single-binary deployments.

Quick Start

Ask your assistant to check for a new Hope Agent version and show the release notes before installing it.

Frequently Asked Questions about ha-self-update

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

FAQPage Schema
How do I check for software updates and view release notes before installing?

To check for software updates, you can request an update check through the conversation flow. The system surfaces the current versus latest version and displays relevant release notes for your review before any installation begins.

How does self-update binary verification work for server daemon deployments?

Self-update binary verification uses Minisign-signed manifest verification to authenticate packages. This cryptographic process ensures the downloaded server daemon binary matches the trusted manifest before any installation or service restart occurs.

Can I safely rollback a package manager update if the new version has bugs?

Yes, you can safely rollback an update if the new version introduces bugs. The rollback process uses mandatory user-confirmation gating, requiring your explicit approval through a Yes/No dialog before reverting the package manager deployment.

Does the self-update process support headless single-binary deployments?

Yes, the self-update process fully supports headless, self-contained single-binary deployments. It works across desktop GUI bundles, server daemons, and single-binary formats using conversation-driven commands for update management.

Why does the software update require manual confirmation before installing?

The software update requires manual confirmation to prevent risky silent upgrades. User-confirmation gating ensures you maintain control over the installation process, requiring a Yes/No dialog approval before applying any changes to the system.

What are the limitations of automated self-updates for desktop applications?

A key limitation is that self-updates cannot bypass user-confirmed gating. Even for desktop applications, the process requires manual Yes/No confirmation for both installs and rollbacks, preventing fully automated background upgrade scenarios.