openclaw - 💡(How to fix) Fix Feature Request: Respect delivery.channel as exclusive target for cron jobs [1 participants]

Problem

When cron jobs are configured with delivery.mode: "announce" and a specific target channel (e.g. delivery.channel: "telegram", delivery.to: "<chat_id>"), the result is broadcast to all surfaces — including the webchat TUI. This means cron job output appears as "System:" messages in the TUI even when the user explicitly configured delivery only for a specific channel.

There is currently no way to send cron output exclusively to the specified target channel without it also appearing in other surfaces.

Steps to Reproduce

1. Create a cron job with delivery.mode: "announce", delivery.channel: "telegram", delivery.to: "<chat_id>"
2. Wait for the scheduled run to fire
3. Observe that the result appears both in Telegram (correct) and in the webchat TUI as a "System:" message (unwanted)

Expected Behavior

When delivery.channel is explicitly set, the cron job output should be delivered only to that channel. The webchat TUI (and any other surfaces) should not receive the output.

Proposed Solution

Treat delivery.channel as an exclusive target: when a specific channel is configured, deliver only to that channel. If delivery.channel is omitted, fall back to broadcasting to all surfaces (current behavior).

This preserves backward compatibility while giving users precise control over where cron output is delivered.

Use Case

User runs multiple cron jobs (security briefings, monitoring, digests) that should deliver exclusively to Telegram. The TUI should stay clean and only show direct interactions, not scheduled job output.