hermes-update

Update a self-hosted Hermes agent on a remote VPS via SSH with backup and rollback.

13|1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/paarths-collab/hstack --skill hermes-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-update
Source: https://github.com/paarths-collab/hstack/tree/main/skills/hermes-update
Command: npx skills add https://github.com/paarths-collab/hstack --skill hermes-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk and manual effort from upgrading a self-hosted Hermes agent on a remote VPS, so you can move to a new version without breaking the gateway or losing wiring.

Core Features & Use Cases

  • SSH-first upgrade workflow: Runs the entire update on the VPS, not on the local machine, which fits remote production deployments.
  • Backup and rollback safety: Creates a backup before changing anything and provides a recovery path if the update fails.
  • Post-update verification: Rechecks the gateway, smoke tests agent responsiveness, and compares wired MCP/platform lists after the bump.
  • Use case: When a new Hermes release is available, use this Skill to pin the target version, reload the gateway correctly, and confirm every integration still works.

Quick Start

Ask the AI to update the Hermes agent on your VPS to the target version, back it up first, reload the gateway, and verify that all wired platforms still respond.

Frequently Asked Questions about hermes-update

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

FAQPage Schema
How do I safely update a self-hosted Hermes agent on a VPS over SSH?

To safely update a self-hosted Hermes agent on a VPS, you need an SSH-based workflow that creates a backup, pins the target version, and reloads the gateway. This ensures the update does not break existing wiring or platform integrations.

What's the best way to rollback a failed Hermes deployment on a remote server?

The best way to rollback a failed Hermes deployment is to use a workflow that creates a backup before applying changes and maintains a recovery path. This allows you to restore the previous configuration if the post-update verification fails.

How do I verify wired integrations after upgrading Hermes?

To verify wired integrations after upgrading Hermes, run smoke tests to check agent responsiveness and compare wired MCP and platform lists. This re-verification confirms that the gateway reload succeeded and all integrations still respond.

Does the Hermes SSH update workflow support both host and container deployments?

Yes, the Hermes SSH update workflow supports both host and container deployments on a remote VPS. It applies pinned version installation and gateway reloads across both environments while maintaining rollback-ready recovery checks.

Can I update Hermes from CLI tools like Claude Code, Codex, or Cursor?

Yes, you can update Hermes using CLI tools like Claude Code, Codex, Cursor, and Gemini CLI. The update workflow runs entirely on the remote VPS over SSH, allowing these clients to trigger the deployment safely.

Why does my Hermes gateway lose platform connections after a version bump?

A Hermes gateway loses platform connections after a version bump if the update lacks proper post-update verification. Rechecking the gateway and comparing wired platform lists ensures every integration still works after the reload.