hermes - 💡(How to fix) Fix Cron: support multi-target delivery [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#13469Fetched 2026-04-22 08:06:19
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×3commented ×1

Fix Action

Fix / Workaround

This means cron jobs that need to deliver to multiple channels (e.g. Telegram + Discord + Slack) have no good workaround -- you either run the same job 3x with different targets (tripling cost and API usage) or accept single-channel delivery.

RAW_BUFFERClick to expand / collapse

Problem

The cron deliver field only accepts a single target. The cron runner also injects a system instruction telling the agent not to use send_message, so even if the skill specifies multiple delivery channels, the agent is told to ignore that.

This means cron jobs that need to deliver to multiple channels (e.g. Telegram + Discord + Slack) have no good workaround -- you either run the same job 3x with different targets (tripling cost and API usage) or accept single-channel delivery.

Proposal

Allow deliver to accept an array of targets:

Backward compatible - a bare string is treated as a single-element array. The cron runner sends the final response to each target independently, with per-target success/failure logging.

extent analysis

TL;DR

Allowing the deliver field to accept an array of targets is the most likely fix to support multiple delivery channels for cron jobs.

Guidance

  • Modify the deliver field to accept an array of strings, where each string represents a target delivery channel.
  • Update the cron runner to iterate over the array of targets and send the final response to each target independently.
  • Implement per-target success/failure logging to track the delivery status for each channel.
  • Ensure backward compatibility by treating a bare string as a single-element array.

Example

// Example of updated deliver field
{
  "deliver": ["Telegram", "Discord", "Slack"]
}

Notes

The proposed solution assumes that the underlying infrastructure and APIs support sending messages to multiple channels. Additional error handling and logging mechanisms may be necessary to handle cases where delivery to one or more channels fails.

Recommendation

Apply workaround: Modify the deliver field to accept an array of targets, as this allows for multiple delivery channels without requiring significant changes to the existing cron job system.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Cron: support multi-target delivery [1 comments, 2 participants]