hermes - 💡(How to fix) Fix feat(cron): add no_header option to suppress 'Cronjob Response' prefix in delivery

Feature Description

When a cron job delivers a message to a messaging platform (e.g. Telegram), the gateway automatically prepends a header like:

Cronjob Response: <job name> (job_id: <id>)
---

There is currently no way to suppress this prefix for specific jobs.

Motivation

For cron jobs that already produce clean, self-contained output (e.g. an update checker that summarizes new commits, a monitoring job that sends a formatted alert), the header is redundant and makes the message feel robotic and impersonal — especially in personal Telegram chats.

Proposed Solution

Add a no_header boolean option to cron job configuration (via cronjob tool and hermes cron create/edit). When set to true, the gateway skips the Cronjob Response: ... prefix and delivers the message as-is.

Example:

deliver: origin
no_header: true

Alternatives Considered

• no_agent=true mode: strips the header but also removes LLM reasoning, which is needed for jobs that summarize or interpret data before sending.
• Workaround with custom script calling the API directly: too complex to maintain.

Use Case

A cron job that runs every 6 hours, fetches new git commits from the Hermes repo, summarizes them via LLM, and sends the summary to Telegram — without the mechanical header cluttering the message.