hermes-home

Configure the persistent Hermes home channel for cron output and notifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents Hermes reminders, cron output, and proactive notifications from disappearing after restarts by configuring a persistent home channel on the VPS.

Core Features & Use Cases

  • Durable notification routing: Stores the home channel in the Hermes environment so messages survive gateway restarts.
  • Multi-platform support: Works with Telegram, Discord, Slack, Mattermost, and Matrix once the platform is already wired.
  • Safe operational workflow: Verifies SSH access, checks Hermes availability, handles idempotency, reloads the gateway correctly, and includes smoke-test and rollback guidance.
  • Use case: Set a stable destination for cron summaries and reminders so the agent can reliably deliver updates to the same chat or room every time.

Quick Start

Ask the agent to configure the Hermes home channel on your VPS for the wired platform using the correct chat or room ID and make it persistent across restarts.

Frequently Asked Questions about hermes-home

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

FAQPage Schema
How do I persist Hermes notifications across gateway restarts on a VPS?

This Skill configures a persistent home channel by writing the HOME_CHANNEL environment variable to ~/.hermes/.env, ensuring cron output and proactive Hermes notifications survive gateway restarts on a VPS.

Why do my Hermes cron output and reminders disappear after a server restart?

Hermes cron output and reminders disappear after a restart when the home channel is not persisted in the environment. Configuring the HOME_CHANNEL variable in ~/.hermes/.env ensures durable notification routing.

Does persistent Hermes notification routing work with Discord and Telegram?

Persistent Hermes notification routing works with Telegram, Discord, Slack, Mattermost, and Matrix. It applies to SSH-managed self-hosted deployments after the chosen platform is already wired to the gateway.

How do I configure the Hermes home channel for cron summaries via SSH?

To configure the Hermes home channel via SSH, write the correct chat or room ID to the HOME_CHANNEL variable in ~/.hermes/.env, reload the gateway with stop and run commands, then verify delivery with a smoke test.

What is the safest way to reload the Hermes gateway after updating notification settings?

The safe way to reload the Hermes gateway after updating notification settings is to verify SSH access, handle idempotency, reload with stop and run commands, and verify delivery with a smoke test, following included rollback guidance.