Hermes Agent Heartbeat

README

# Hermes Agent Heartbeat Plugin

OpenClaw-style persistent heartbeat for Hermes Agent messaging sessions.

The plugin does **not** create a cron agent and does not modify Hermes core. It
binds to the configured Telegram thread on the first real inbound event, then
routes synthetic heartbeat events through the existing gateway session. The
session transcript, memory, prompt cache, and model state are therefore reused.

## Install — one line

```bash
hermes plugins install --enable megamen32/hermes-agent-heartbeat
```

## Configure

Replace the chat/thread values and prompt path with your own:

```bash
hermes config set agent_heartbeat.enabled true
hermes config set agent_heartbeat.interval_seconds 900
hermes config set agent_heartbeat.platform telegram
hermes config set agent_heartbeat.chat_id '-1000000000000'
hermes config set agent_heartbeat.thread_id 123
hermes config set agent_heartbeat.prompt_file "$HOME/.hermes/heartbeat/HEARTBEAT.md"
```

For a copy-paste shell continuation form:

```bash
hermes config set agent_heartbeat.enabled true \
  && hermes config set agent_heartbeat.interval_seconds 900 \
  && hermes config set agent_heartbeat.platform telegram \
  && hermes config set agent_heartbeat.chat_id '-1000000000000' \
  && hermes config set agent_heartbeat.thread_id 123 \
  && hermes config set agent_heartbeat.prompt_file "$HOME/.hermes/heartbeat/HEARTBEAT.md"
```

The prompt file is re-read on every cycle. Return `[SILENT]` when no user-visible
message is needed; Hermes suppresses that intentional silence marker.

The plugin is opt-in and clamps the interval to 60 seconds through 24 hours.

## What it solves

Cron runs normally start a detached fresh session. This plugin instead reuses
the live gateway routing key, so periodic work continues in one conversation
with the existing transcript and memory.

## Repository

This repository is intended to be installed as a Hermes plugin. It contains no
credentials and no production-specific host configuration.