Multi-destinations delivery within a single cron job

[tropic barn]

Example: A cron job runs every morning and performs analysis work - Report A is sent to Client A through telegram. Report B is sent to Client B through Slack.

Workflow ends with send_message:telegram <report A> and send_message:slack <report B> and works well when it is triggered manually.

However, the job in a cron fails because the cron system wraps every scheduled execution with instructions similar to this:

[IMPORTANT: You are running as a scheduled cron job. DELIVERY: Your final response will be automatically delivered to the user — do NOT use send_message or try to deliver the output yourself. Just produce your report/output as your final response and the system handles the rest. …]

[tidal echo]

Current cron behavior supports multiple delivery targets, but only for the same final response.

So deliver=telegram:...,slack:... can send one report to both places. It does not let one cron run produce report A for Telegram and report B for Slack through auto-delivery.

For different content per destination, the natural tool would be send_message, but current cron/scheduler.py disables the messaging toolset for cron runs and the cron prompt explicitly tells the agent not to use send_message for delivery. That is why this feels contradictory.

There are already related PRs for this area:

https://github.com/NousResearch/hermes-agent/pull/21438
https://github.com/NousResearch/hermes-agent/pull/7388
https://github.com/NousResearch/hermes-agent/pull/26292
https://github.com/NousResearch/hermes-agent/pull/30561

For now, use separate cron jobs if the destinations need different content. Use multi-target deliver only when the same final report should go to multiple places.