From 29f52dfcb3e94f064d43ad2711fb1554105c1542 Mon Sep 17 00:00:00 2001 From: tiennm99 Date: Wed, 7 Oct 2026 17:48:10 +0700 Subject: [PATCH] docs(hermes): record cron.wrap_response off so deliveries carry only the job output --- hermes/README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/hermes/README.md b/hermes/README.md index 8fa92c7..f76693b 100644 --- a/hermes/README.md +++ b/hermes/README.md @@ -87,6 +87,16 @@ one conversation with the bot, overriding `group_sessions_per_user`; every message lands in `state.db`, and each reply carries the observed backlog to the model provider. +## Scheduled jobs + +Cron deliveries carry only the job's own output: `cron.wrap_response` is +`false` in `/opt/data/config.yaml`, set with +`/opt/hermes/.venv/bin/hermes config set cron.wrap_response false`. Upstream +defaults it to `true`, which wraps every delivery in a +`Cronjob Response: ` header with the job ID and a "To stop or manage +this job" footer. It applies to every job; with it off, a job is managed by +asking the bot by name. + ## Storage | Volume | Mount | Holds |